Relay stream close race conditions and threading fixes

NousResearch/hermes-agent · cluster 132048 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These issues and pull requests address race conditions and threading problems that occur when closing relay-managed streams, particularly around interrupted generators and off-loop reads. The work targets multiple close-path seams where blocked iterators or unread data could cause unsafe behavior.

Open issues1

  • Issue#132048[Bug]: Relay-managed plain-generator stream close races blocked iterator after interrupt

Open PRs2

  • PR#132059fix(relay): drain the off-loop provider read before closing the raw stream
  • PR#132064fix(agent): close an interrupted relay provider stream on its owning thread

1 PR closed without merging

From the close comments: duplicate 1

  • #132080 fix(relay): wait out sync-generator busy window on both close seams (#132048) · duplicate → #132059, #132064
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

Subsystem
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.