# NousResearch/hermes-agent · Thread-safety fix for poll timestamp access

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #23096: bug: _last_poll_timestamps read/write in _poll_once missing lock protection

## Prior & competing PRs

- **#23174: fix(tools): protect _last_poll_timestamps with self._lock in EventBridge**. closed without merge · fix tier `suggested`
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#23219`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#23219: Fix/mcp poll timestamps lock**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#23107`, `#23096`

## Fix status

- No merged fix on record.
- Subsystem: `mcp`