Latest Results
Save state trees with one atomic lock-checked script instead of WATCH
The redis client is created with retry_on_error=[RedisError], so when EXEC
returned nil for a changed lock, redis-py reconnected and re-ran the
transaction without the WATCH and the stale write landed anyway; the mock
did not model that, only a real redis showed it.
The save is now a single EVAL: the script compares the lock id, writes every
touched state with its expiration, and returns the lock's PTTL, or nil
without writing when the lock changed hands. That makes the check and write
atomic on the server, safe under command retries, and one round trip instead
of four (WATCH, GET, PTTL, EXEC). The mock emulates that script, and the
WATCH-specific retry and tests go away with it.
Also fall back to the full snapshot when a hydrate payload's hash list has a
different length than the compiled states, instead of failing the event.claude/reflex-load-performance-0sqaes Latest Branches
0%
claude/blockbuster-reflex-analysis-06qhgm 0%
claude/reflex-load-performance-0sqaes 0%
codex/perf-literal-dispatch-cache © 2026 CodSpeed Technology