Yuneng Jiang 288d403529 [Fix] Preserve in-memory spend updates when Redis rpush fails ...

store_in_memory_spend_updates_in_redis drained the in-memory queues
into local variables before the rpush pipeline. If rpush raised (cloud
Redis hiccup, timeout, connection blip), those already-drained
transactions were garbage-collected with the scheduler job, silently
losing all spend aggregated during that tick.

Wrap the rpush in try/except. On failure, re-enqueue the aggregated
transactions into their respective in-memory queues so the next
scheduler tick retries.

Add a unit test that seeds real queues, simulates an rpush failure,
and asserts the transactions land back in-memory.

2026-04-22 14:10:40 -07:00

..

test_base_update_queue.py

style: run black formatter on files from main merge

2026-04-17 13:02:59 -07:00

test_daily_spend_update_queue.py

…

test_pod_lock_manager.py

style: run black formatter on files from main merge

2026-04-17 13:02:59 -07:00

test_redis_update_buffer.py

[Fix] Preserve in-memory spend updates when Redis rpush fails

2026-04-22 14:10:40 -07:00

test_spend_update_queue.py

…

test_tool_discovery_queue.py

feat(proxy): tool policies - auto-discover tools + policy enforcement guardrail (#22041)

2026-02-24 16:27:06 -08:00