NousResearch/hermes-agent
Gateway notification on QQBot reconnect exhaustion and Telegram retry state
Cluster 29005 · gateway. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
4items grouped
- Known?
- Yes. 4 related items grouped here, 0 issues 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
- 1 issue and 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese members center on the QQBot adapter not notifying the gateway when reconnect attempts are exhausted, and on Telegram's retrying state not appearing in runtime status. Several PR titles propose changes for both, referencing #29005, while one issue-style title describes the problem.
Open issues1
- Issue#29005QQBot adapter does not notify gateway on reconnect exhaustion; Telegram retry state not reflected in runtime status
Open PRs1
- PR#72673fix(qqbot): notify gateway watcher on reconnect exhaustion instead of silent deathFix/qqbot notify gateway
2 PRs closed without merging
From the close comments: superseded by another PR 1 · other 1
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.50: 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
- Subsystem
- gateway
- Closed issues
- 0
- Attempts
- 2 PRs closed without merging