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
{{ message }}
Repository navigation
Slots gate: clear holds used up after a failed store read; fewer repeated warnings #574
A hold used up after a failed store read stays in the store file (apps/server/src/slots/SlotGate.ts, near line 250). The next good read hides it only in memory; stored.used is never called for it. After a server restart it counts again until it runs out, so the gate counts one agent too many for a while. Fix: return those keys and clear them through clearStored outside the semaphore, as acquire already does. Add a test: start while the store is unreadable, then a good read, then a new gate on the same store file: the hold is not counted.
Repeated warnings while the store cannot be read (SlotGate.ts, near line 257). Every gate call and every observation logs a warning. Log only when the reason changes, as WaitService.unavailable does.
State question for the fix: runs again (clearing twice is harmless), stopped half-way (cleared in memory but not on disk), old or empty store file.
Activity
slots: clear holds used up after a failed store read; warn once per r…
slots: clear holds used up after a failed store read; warn once per r…