You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test(run-engine): repro for stale worker queue entry after sweeper ack
Adds a failing test in concurrencySweeper.test.ts that demonstrates an
inconsistency between the worker queue list and the message body store:
- Fast-path enqueue RPUSHes the messageKey value onto the worker queue list
and SADDs the run into currentConcurrency.
- The sweeper marks the run as completed (via test callback) and processMarkedRun
acks with removeFromWorkerQueue: false, which DELs the message body but skips
the LREM on the worker queue list.
- A subsequent blocking dequeue BLPOPs the stale messageKey, the GET returns
nil, and the dequeue path emits "Failed to dequeue message from worker queue"
with workerQueueLength: 0.
The test asserts that the dequeue path does not log this error after the
sweeper has acked the run.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments