Cairn

WeCom WebSocket reconnection reliability and safety fixes

NousResearch/hermes-agent · cluster 33287 · gateway

Data as of

7 open items. Fix attempted, not merged.

The short answer

4open issues
3open PRs
13items grouped
Known?
Yes. 13 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 5 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
4 issues and 3 PRs.

This cluster focuses on bugs and fixes in the WeCom adapter's WebSocket connection lifecycle, specifically around exception-unsafe cleanup, missing connection states in handshake handling, silent reconnection failures, and insufficient retry logging.

Open issues4

  • Issue#33287WeCom adapter: connection degradation after May 15 gateway infrastructure changes
  • Issue#55491WeCom _cleanup_ws should be defensive against internal exceptions
  • Issue#64512[Bug] WeCom adapter: _cleanup_ws() exception-unsafe → permanent reconnect failure + silent loop death
  • Issue#64703fix(wecom): _wait_for_handshake missing CLOSING state causes permanent reconnect failure after mass restart

Open PRs3

  • PR#55516fix(wecom): guard _cleanup_ws against exceptions from resource close()
  • PR#56463fix(gateway): make WeCom _cleanup_ws defensive against partially-initialized adapters (#55491)
  • PR#64716fix(wecom): add CLOSING state to _wait_for_handshake terminal handler

5 PRs closed without merging

From the close comments: duplicate 2 · superseded by another PR 1 · other 2

  • #47606 fix(wecom): bound reconnect attempts and log retries · superseded by another PR → f2a7adb, #47572
  • #47622 fix(wecom): improve reconnection logging with attempt counts (#47572) · other
  • #64678 fix(wecom): make _cleanup_ws() exception-safe to prevent permanent disconnect (#64512) · other → #64184
  • #64727 fix(wecom): add CLOSING state to _wait_for_handshake auth guard (#64703) · duplicate → #64716
  • #64729 fix(wecom): make _cleanup_ws exception-safe (#64512) · duplicate → #64678
Closed issues · 1
  • Closed#47572[BUG] WeCom adapter: WebSocket reconnection may fail silently without logging success or failure
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.12: the share of item 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.

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 Lab

At a glance

Subsystem
gateway
Closed issues
1
Attempts
5 PRs closed without merging

For your agent

The same facts, typed.

cluster/33287.json
cluster/33287.md