Cairn
NousResearch/hermes-agent

Concurrent auxiliary client cache collision bug fix

Cluster 96491 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 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 1 PR.

A bug where concurrent auxiliary calls sharing the same cache key could cause in-flight clients or streams to be incorrectly closed, leading to spurious connection or compression errors. These items address identifying and fixing that race condition.

Open issues1

  • Issue#96491[Bug] Concurrent same-key auxiliary calls: _store_cached_client closes in-flight client → compression fails with spurious Connection error

Open PRs1

  • PR#96509fix(auxiliary): stop concurrent calls from aborting in-flight streams

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #96613 fix(auxiliary_client): stop closing in-flight clients on cache key collision (#96491) · superseded by another PR → #96830
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/96491.json
cluster/96491.md