NousResearch/hermes-agent
Timeout defaults and stream-timeout behavior for compression and Codex
Cluster 22986 · agent/transports. Data as of
Nothing open on GitHub. Fix attempted, not merged.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskTwo members propose raising the default auxiliary compression timeout (120s to 300s), while a third reports a higher rate of Codex APIConnectionError retries after v0.13.0 and suspects strict stream-timeout enforcement. The members are related by timeout behavior, but the titles alone do not show that the compression timeout and the Codex retry issue share a cause.
Open issues0
Open PRs0
2 PRs closed without merging
From the close comments: done elsewhere 1 · duplicate 1
Closed issues · 1
- Closed#22986[Bug] Codex APIConnectionError retry rate ~8x higher post-v0.13.0; persists with #12953 applied; suspected commit 5533ad764 strict stream-timeout enforcement
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- agent/transports
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging