Avatar for the reflex-dev user
reflex-dev
reflex
BlogDocsChangelog

Performance History

Latest Results

Merge remote-tracking branch 'origin/explicit-event-id-minification' into late-bound-wire-names
benedikt-bartscher:late-bound-wire-names
11 hours ago
Merge remote-tracking branch 'upstream/main' into explicit-event-id-minification Ported upstream changes into the resolver-aware code: - Context template: hydrate_and_load (#7064) gets a resolved wire name in InternalEventNames (replacing hydrate), alongside upstream's state schema and initial state hashes. state.js reads app.hydrate_and_load and app.update_vars_internal instead of hardcoded default names, and the handshake query (token + scheme) is built for the warm-up socket too. - State reads use upstream's useStateContext (#7441), keyed by the state's resolved full name, into the prefixed local. - Upstream made unknown substates non-fatal (#7435) and dropped backend_state_mismatch; the fatal minification scheme mismatch keeps its own flag (backend_scheme_mismatch) gating events, updates and reconnects. - The frontend state schema hash (#7553) hashes resolver-independent names; the scheme digest already covers the wire names. - The processor's hydrate/hydrate_and_load/on_load_internal lookups cache handlers, not names, so they follow a resolver installed later. - BaseStateToken._state_key keys by the resolver-independent name. - get_substate keeps upstream's loop but only lets the first segment name the state itself; get_name/get_full_name stay function-wide caches so a resolver install clears every class, and also clears _get_substate_path. - on_connect sets up per-SID state before upstream's new first await. - pyStrAt avoids Array.prototype.at, which the state.js tests forbid.
benedikt-bartscher:explicit-event-id-minification
12 hours ago
Merge remote-tracking branch 'upstream/main' into late-bound-wire-names Ported upstream changes into the resolver-aware code: - Context template: hydrate_and_load (#7064) gets a resolved wire name in InternalNames (replacing hydrate), alongside upstream's state schema and initial state hashes. state.js reads app.hydrate_and_load and app.update_vars_internal instead of hardcoded default names, and the handshake query (token + scheme) is built for the warm-up socket too. - State reads use upstream's useStateContext (#7441), keyed by the state's resolved full name, into the branch's prefixed local. - Upstream made unknown substates non-fatal (#7435) and dropped backend_state_mismatch; the fatal minification scheme mismatch keeps its own flag (backend_scheme_mismatch) gating events, updates and reconnects. - The frontend state schema hash (#7553) hashes resolver-independent names; the scheme digest already covers the wire names. - The processor's hydrate/hydrate_and_load/on_load_internal lookups cache handlers, not names, so they follow a resolver installed later. - BaseStateToken._state_key and client storage application (_apply_client_storage_vars) use default names and wire var keys. - get_substate keeps upstream's loop but only lets the first segment name the state itself; get_name/get_full_name stay function-wide caches so a resolver install clears every class, and also clears _get_substate_path. - on_connect sets up per-SID state before upstream's new first await. - pyStrAt avoids Array.prototype.at, which the state.js tests forbid.
benedikt-bartscher:late-bound-wire-names
12 hours ago

Latest Branches

CodSpeed Performance Gauge
+6%
Minify state var names and allow installing a name resolver after states exist#7337
12 hours ago
8cdbb67
benedikt-bartscher:late-bound-wire-names
CodSpeed Performance Gauge
+5%
12 hours ago
55bbc45
benedikt-bartscher:explicit-event-id-minification
CodSpeed Performance Gauge
0%
12 hours ago
1f47ed1
benedikt-bartscher:lambda-callback-readonly-code
© 2026 CodSpeed Technology
Home Terms Privacy Docs