Peer DM timeout misclassified as unreachable peer
Cluster 113099. Data as of
Nothing open on GitHub. Fix merged in #116885 on 20 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #116885. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116885. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes address a bug where a timed-out peer direct message is incorrectly reported as the peer being unreachable, rather than as a slow or still-running response. This misclassification can cause the sender to resend a message that was already delivered.
Open issues0
Open PRs0
Fixes on record
-
#116885 fix(peer): a timed-out peer DM says the turn was accepted and is still running, not that the peer is unreachable (#113099, salvage #113102)
files:
hermes_cli/subcommands/peer.py,tests/hermes_cli/test_peer_dm_reporting.py,website/docs/user-guide/bot-mode.md
1 PR closed without merging
From the close comments: done elsewhere 1
-
#113102 fix(peer): a timed-out peer DM is a slow answer, not an unreachable peer · done elsewhere →
#116885,#113099
Closed issues · 1
- Closed#113099A timed-out peer DM is reported as an unreachable peer, so the sender resends an already-delivered message
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
- #116885
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Sep 2026