Cairn
NousResearch/hermes-agent

Thread-safety fix for poll timestamp access

Cluster 23096 · mcp. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 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
Nothing open on GitHub.

These items address a concurrency bug where reads and writes to _last_poll_timestamps in the EventBridge polling logic were not protected by a lock. The work involves adding proper lock protection around that shared state.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

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

  • #23174 fix(tools): protect _last_poll_timestamps with self._lock in EventBridge · superseded by another PR → #23219
  • #23219 Fix/mcp poll timestamps lock · duplicate → #23107, #23096
Closed issues · 1
  • Closed#23096bug: _last_poll_timestamps read/write in _poll_once missing lock protection
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
mcp
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/23096.json
cluster/23096.md