mirror of
https://github.com/hanzoai/forge.git
synced 2026-10-30 15:00:39 +00:00
zeekayandHanzo Dev
63eb304f1c
Correction to the previous commit. It said the queue package was "green three runs running" — that was true when I ran it and false when I pushed it, because TestWorkerPoolQueueActiveWorkers is load-sensitive and I had only re-timed it, not fixed it. The claim should not have been made on three passes of something I had just changed the timing of. The test asserted worker counts a fixed interval after pushing. That interval was tuned to the in-memory backend, where a push was a channel send. A durable queue writes to disk first, and under full-package load that write is not a fixed distance away — so it passed alone and failed in the suite. Raising 50ms to 150ms moved the boundary without removing it. It now polls to a 5s deadline and reports what it last saw. These assertions are about the state the pool REACHES — one worker starts and becomes active, three scale up, all go idle when the work is done — not about the moment it gets there. Both blocks converted; no tuned sleeps left in the file. 5 consecutive full-package runs green, rest of the tree green. Co-authored-by: Hanzo Dev <[email protected]>