NousResearch/hermes-agent
Fix KeyError from concurrent PTY session reaping
Cluster 106400. Data as of
Nothing open on GitHub. Fix merged in #106511 on 9 Sep 2026. Check it covers your case.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #106511. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #106511. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A KeyError could occur when concurrent reap operations attempted to remove the same key from the PTY session registry. The fix makes reaping skip already-removed keys rather than raising an error.
Open issues0
Open PRs0
Fixes on record
-
#106511 fix(cli): concurrent PTY reaps no longer raise KeyError into the terminal websocket (#106400, salvage #106415)
files:
hermes_cli/pty_session.py,tests/test_pty_session.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#106415 fix(cli): concurrent PTY reaps skip already-popped keys instead of raising · merged via another change →
95cfcba,#106511
Closed issues · 1
- Closed#106400KeyError in PtySessionRegistry.reap_idle: concurrent reap pops same key (observed with NUL byte in session key)
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.00means 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 LabAt a glance
- Merged PRs
- #106511
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 9 Sep 2026