NousResearch/hermes-agent
WeCom errcode 846609 reconnect-gap delivery handling
Cluster 29667 · gateway. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
3items grouped
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR 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 taskAll three members concern WeCom message sends affected by ercode/errcode 846609 when the WebSocket disconnects and reconnects before a reply. One is an issue describing silent delivery failures, and two are pull requests proposing redelivery or retry after reconnect; their outcomes are not stated.
Open issues1
- Issue#29667WeCom: ercode 846609 — session-level WebSocket disconnects before reply, causing silent delivery failures
Open PRs1
- PR#114751fix(wecom): redeliver sends lost in the 846609 reconnect gap
1 PR closed without merging
From the close comments: other 1
-
#29731 fix(wecom): retry on ercode 846609 after WebSocket reconnect · other →
#24790
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
- Subsystem
- gateway
- Closed issues
- 0
- Attempts
- 1 PR closed without merging