Cairn
NousResearch/hermes-agent

QQ Bot WebSocket CLOSING handling and CPU spin

Cluster 41872 · gateway. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 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 2 PRs.

These members all concern the QQ Bot adapter's handling of aiohttp's WSMsgType.CLOSING message type, which is reported to cause 100% CPU spin. One is an issue describing the behavior, and the others are pull requests proposing handling for it in the event-reading code; nothing here indicates their status.

Open issues1

  • Issue#41872QQ Bot adapter spins at 100% CPU when aiohttp returns WSMsgType.CLOSING

Open PRs2

  • PR#41883fix(qqbot): handle WebSocket CLOSING in _read_events
  • PR#83778fix(qqbot): handle WSMsgType.CLOSING to stop CPU spin

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #41937 fix(qqbot): handle WSMsgType.CLOSING to prevent CPU spin (#41872) · superseded by another PR → #41883, #41872
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.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
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/41872.json
cluster/41872.md