reflex-dev/reflex - CodSpeed

reflex

Blog Docs Changelog

Performance History

Latest Results

test(events): state why the cached chain is re-asserted after the event actions call

FarhanAliRaza:farhan/event-chain-interning

3 minutes ago

Address review of the VarData field dependency grouping Three points from the automated review of c67a9bc69: - `field_dependencies` was inserted before `imports` in `VarData.__init__`, so a caller passing four or more arguments positionally would have bound `imports` to the new parameter. No caller in the repo does, but VarData is public surface in reflex-base. Move it after the existing parameters. - The new composite-dependency test left its consumer registered in both source states' `_var_dependencies` and `_potentially_dirty_states`, which outlive the test; a later test dirtying either field would resolve the stale entry and raise on the missing substate. Tear them down, as the router dependency tests nearby already do. - The news fragment claimed existing readers are unaffected. That holds for a multi-state composite -- the old merge dropped other states' fields, so `field_names` reports the same thing it did before -- but not for a VarData carrying field names and no state, which used to be folded into the first state's list and now sits under its own "" key. Point readers at `field_dependencies` instead of claiming blanket compatibility. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mwk1pagH3KZ884Xw55BNMh

claude/router-vars-refactor-7j1305

4 minutes ago

fix: close the health-check Redis client on lifespan shutdown Hold the health-check client in a module slot instead of functools.cache and release it from the lifespan cleanup next to the state-manager and token-manager clients. A new lifespan in the same process starts with a fresh client, so the first probe after a restart no longer fails on a connection bound to the previous event loop, and shutdown leaves no unclosed socket.

FarhanAliRaza:farhan/health-redis-reuse

5 minutes ago

docs: rename the dynamic form handler so it does not shadow State.add_field

FarhanAliRaza:fix-reserved-state-names

5 minutes ago

Group VarData field dependencies by owning state `field_names` was a flat tuple paired with a single `state`, so merging a var built from one state's field with a var built from another's dropped the second: `VarData.merge` kept only the fields whose state matched the first non-empty one. A computed var depending on such a composite var never tracked the other state's field and went stale when it changed. Make the canonical form a `Mapping[str, tuple[str, ...]]` of state to its field names, unioned across merges, and register dependencies against every state in it -- in `_add_static_dep`, in `add_dependency`, and in `DependencyTracker`, all three of which previously collapsed a composite var to one state. `state`, `field_names` and `field_name` stay as fallback accessors reporting the first state and its first field, which is what the remaining readers in `state.py`, `exceptions.py` and the memoize plugin want. The mapping is a plain dict rather than a `MappingProxyType`: VarData is pickled along with the states holding it, and mappingproxy cannot be pickled. It is built fresh per VarData and never mutated afterwards. Verified against a var spanning two states: the second state's field goes from untracked to tracked. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mwk1pagH3KZ884Xw55BNMh

claude/router-vars-refactor-7j1305

11 minutes ago

Drop the record_values parameter from get_delta The ContextVar already carries the flag through the whole traversal, so the parameter was a second way to say the same thing and the only public surface either method needed to grow. `get_delta` and `_get_resolved_delta` go back to taking nothing but `self`, which is also the signature downstream monkeypatches assume, and `_suppress_delta_recording` takes no argument now that the one caller only ever suppresses. test_delta_methods_take_no_arguments guards the signatures directly, so reintroducing a parameter fails here rather than downstream. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fhci3gBdffJ84uzNGKrY3n

claude/rx-var-cache-false-optimize-g7hds3

12 minutes ago

fix: reuse one Redis client for /_health probes get_redis_status() built a new Redis client and connection pool on every call, so each /_health probe performed a full TCP connect and close against Redis. Orchestrators probe this endpoint every few seconds, which on Azure Container Apps drove SNAT port exhaustion through TIME_WAIT churn. Cache the health-check client with functools.cache so every probe is a PING over an established connection. The client reconnects on its own after an outage, so the reported status still flips to False and back. Fixes #7178

FarhanAliRaza:farhan/health-redis-reuse

24 minutes ago

fix(compiler): drop the event chain and wrapper caches at the start of each compile

FarhanAliRaza:farhan/event-chain-interning

30 minutes ago

Latest Branches

-2%

perf(events): share one chain per handler and trigger across call sites#7122

10 minutes ago

f0255e8

FarhanAliRaza:farhan/event-chain-interning

+1%

perf: split router into per-field base vars; gather connection-static router data at connect#7068

12 minutes ago

8b4a59d

claude/router-vars-refactor-7j1305

-3%

fix: reuse one Redis client for /_health probes#7187

11 minutes ago

bf26dc5

FarhanAliRaza:farhan/health-redis-reuse

© 2026 CodSpeed Technology

Home Terms Privacy Docs