NousResearch/hermes-agent

Async semaphore cache tied to wrong event loop

Cluster 93772 · agent. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues 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
1 issue and 0 PRs.

These issues and fixes address a bug where cached auxiliary async semaphores could be reused across event loops, including dead ones. The work scopes semaphore caching to the owning event loop to prevent stale state reuse.

Open issues1

  • Issue#93772Auxiliary async semaphore cache can reuse state from a dead event loop

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1

  • #93880 fix(agent): scope auxiliary semaphores to event loops · done elsewhere
  • #93902 fix(auxiliary): bind cached async semaphores to their owning event loop · duplicate → #93880
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.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
2 PRs closed without merging

For your agent

The same facts, typed.