Cairn
NousResearch/hermes-agent

Auxiliary zero/non-positive timeout handling fixes

Cluster 33227 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

0open issues
2open PRs
5items grouped
Known?
Yes. 5 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
0 issues and 2 PRs.

These issues and pull requests address a bug where zero or non-positive timeout values cause immediate failures in auxiliary operations. The fixes involve treating such values as disabled or omitting them rather than applying them literally.

Open issues0

No open issues.

Open PRs2

  • PR#33229fix(auxiliary): treat zero timeouts as disabled
  • PR#33235fix(auxiliary): treat zero timeouts as disabled

2 PRs closed without merging

From the close comments: duplicate 2

  • #33255 fix(auxiliary): omit non-positive request timeouts · duplicate → #33229, #33227, #33235
  • #33714 fix(agent): ignore non-positive auxiliary timeouts · duplicate → #33229, #33227, #33255
Closed issues · 1
  • Closed#33227Auxiliary compression can fail immediately when timeout is set to 0
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.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Subsystem
agent
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/33227.json
cluster/33227.md