Cairn
NousResearch/hermes-agent

Relay deadline chain and bot reply timeout fixes

Cluster 113107. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 3 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.

These members address bugs in the relay's deadline propagation, where reply waiters could outlive their host context and bot_mode turn wait seconds were not respected. The work involves identifying and patching the broken deadline chain behavior.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: duplicate 1 · superseded by another PR 1 · other 1

  • #113246 fix(relay): preserve delivery deadline chain · other → #113107
  • #113527 fix(relay): honor configured bot reply deadlines · superseded by another PR
  • #113528 fix(relay): honor configured bot reply deadlines · duplicate → #113246, #113107
Closed issues · 1
  • Closed#113107The relay's deadline chain does not hold: the reply waiter outlives its host, and the client deadline ignores bot_mode.turn_wait_seconds
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.50: 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

Closed issues
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/113107.json
cluster/113107.md