reflex-dev/reflex - CodSpeed

reflex

Blog Docs Changelog

Performance History

Latest Results

Sync uv.lock with the testing extra in pyproject.toml (#7047) PR #7008 added the testing optional-dependency group but left uv.lock without the corresponding requires-dist entries and provides-extras entry, so every uv command rewrote the lock file. Regenerated with `uv lock`; only the reflex package metadata changed, no dependency versions were bumped. Claude-Session: https://claude.ai/code/session_01KpSPsdMoxxXp3xqsDUpvVS Co-authored-by: Claude <noreply@anthropic.com>

main

29 minutes ago

Sync uv.lock with the testing extra in pyproject.toml PR #7008 added the testing optional-dependency group but left uv.lock without the corresponding requires-dist entries and provides-extras entry, so every uv command rewrote the lock file. Regenerated with `uv lock`; only the reflex package metadata changed, no dependency versions were bumped. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KpSPsdMoxxXp3xqsDUpvVS

claude/laughing-volta-tfqz93

1 hour ago

Update scaling_state.md to remove events.py reference Removed reference to events.py and clarified state.py's role.

docs/scaling-state

1 hour ago

Preserve RegistrationContext in telemetry worker threads (#6960) * tests: scope the shared-context config load count to the test's own threads test_get_config_loads_once_for_shared_context patches reflex_base.config._load_config and asserts it ran exactly once. The counter was process-wide, so any background thread that called get_config() inside the patched window was counted as a duplicate load of the shared context. The telemetry worker thread does exactly that: _process_event -> _send -> _prepare_event -> get_event_defaults -> get_bun_version -> path_ops.get_bun_path -> get_config(). That thread carries no RegistrationContext, so ensure_context() creates a fresh one and loads the config for it. When an event queued by an earlier test drains during this test, load_count reaches 2 and the assert fails (seen on Windows CI). Count only loads made from the test's worker threads, via a thread-local marker, so an unserialized load path for the shared context still fails the test while unrelated background loads are ignored. * telemetry: run queued work under the submitter's RegistrationContext The telemetry worker thread carries no RegistrationContext, so a config lookup during event collection (_prepare_event -> get_event_defaults -> get_bun_version -> path_ops.get_bun_path -> get_config()) attached a throwaway context to the worker and re-imported rxconfig.py off-thread — duplicating work the caller had already done, against a config the app is not using, and mutating sys.path from a background thread while doing it. _submit now captures the caller's RegistrationContext (without attaching one to a caller that has none) and _run_suppressed attaches it for the duration of the job, resetting it afterwards so a context never leaks into the next job on the reused worker thread. Collection therefore reuses the already-loaded Config instead of loading its own. Verified across the unit suite: instrumenting _load_config to log calls from non-main threads reported one such load before this change and none after. * changelog: add news fragment for the telemetry registration-context fix * telemetry: document the context-less-job caveat in _run_suppressed --------- Co-authored-by: Claude <noreply@anthropic.com>

main

1 hour ago

improve hybrid property (#6812) * improve hybrid property * some fixes * wip * more hp fixes * fix(vars): resolve hybrid property alias targets from the bound origin, skip pydantic test without pydantic * cubic nits * fix conflicts * wtf * fix: keep aliased hybrid_property accessors when a decorator redeclares the property's name * revert this * also revert this * fix: bind a forked hybrid_property under its own redeclared name instead of its ancestor's * revert leftover test_log parametrization from the reverted CLI import fix * fix: don't shadow an inherited hybrid property with state storage * fix: document and fix property setter and deleter * python 3.10 compat * fix: correct base linearization and inherited field defaults * fix: linearize by identity and don't swallow field factory errors

main

1 hour ago

docs: make both identity samples runnable as written The handler sample called `@rxe.event` without importing `reflex_enterprise as rxe`, so copying it raises `NameError` at import, before the handler could run. The component sample above it had the same flaw and was not reported: `rx.hstack`, `rx.avatar` and `rx.text` with no `import reflex as rx`. Fixed both, since a reader copies whichever one matches what they are doing and neither would have worked. The page's own `python exec` block imports rx for the screenshot calls, which is what hid this: the samples render fine on the page while being incomplete for anyone pasting them into an app.

khaleel/docs-user-authentication

2 hours ago

docs: format the handler sample, and relock for the testing extra Two unrelated things the same pre-commit run wanted. `ruff-format` also formats python blocks inside docs, and the sample I added in the previous commit was missing the blank line before its decorator. That is why the docs commit before it passed and this branch then went red on a change that touched one markdown file. The lock is stale against `pyproject.toml`, which has declared a `testing` extra since #7008 while `uv.lock` still says `provides-extras = ["db", "pydantic"]` and carries no `extra == 'testing'` entries at all. Nothing in this branch can affect dependency resolution -- it is two docs files -- so this is main's drift surfacing once `uv` began writing the field. Relocked rather than left, since every branch cut from here hits it.

khaleel/docs-user-authentication

2 hours ago

docs: use the real current-user API, not the authz check's argument `auth_user.email` and friends are not a public surface. `auth_user` is the name of the argument an *authorization check* callable receives, and I lifted it out of an internal docstring and presented it as the way an app reads its signed-in user. Apps generated from that would fail on attribute access. The supported interface, per `docs/enterprise/auth/example-app.md` and `reflex_enterprise/auth/user_state.py` (where `User = AuthUserState`): * `User.name` / `.email` / `.sub` / `.picture` are Vars, for rendering. * `await User.current()` returns the claims dict inside an event handler, or `None` when anonymous. Both are shown, split by what the reader is doing rather than listed as one set, since which of the two is correct depends on where the code runs. Anything beyond the common claims wants a computed var on an `AuthUserState` subclass, so the page points at the Authentication guide rather than restating it.

khaleel/docs-user-authentication

2 hours ago

Latest Branches

0%

Sync uv.lock with the testing extra in pyproject.toml#7047

2 hours ago

6036dd1

claude/laughing-volta-tfqz93

0%

docs: add guidance for scaling state#6898

1 hour ago

7c580aa

docs/scaling-state

0%

docs: add a User Authentication page for brokered app sign-in#7046

2 hours ago

b9987cf

khaleel/docs-user-authentication

© 2026 CodSpeed Technology

Home Terms Privacy Docs