Claude fb212156f3 fix(stream): mark flushed events _replayed, add Redis hot-path breaker ... Critical: last round's fence-flush fix (keep the queue in the map while draining) turned into an infinite loop because every shifted event went back through chatEventHandler's fence-check branch and was re-queued into the same queue we were trying to drain. Mark each flushed event `_replayed = true` before dispatch so the chatEventHandler fence-buffering branch short-circuits. Re-entrancy ordering is still preserved: live frames arriving during an await inside a flushed-event's handler still don't carry `_replayed` and continue to buffer into the same queue, staying ordered after the current flush batch. Warning: under sustained Redis slowness every emit was paying 100ms on INCR and another 100ms on XADD+EXPIRE, so live token delivery could stall 200ms/frame during an outage. Added a module-level circuit breaker that trips after 3 consecutive failures/timeouts and short-circuits the hot-path Redis calls for a 10s cooldown window. First successful call after cooldown resets the counter. Replay reads deliberately bypass the breaker because they're user-initiated and worth the slower timeout.		2026-04-15 06:44:35 +00:00
..
main.py	fix(stream): mark flushed events _replayed, add Redis hot-path breaker	2026-04-15 06:44:35 +00:00
utils.py	refac	2026-03-22 05:48:05 -05:00