Discord reconnect leaving zombie websocket connections, duplicate responses
Cluster 18187. Data as of
Nothing open on GitHub. Fix merged in #18758 on 2 May 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #18758. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #18758. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The members share one theme: the Discord adapter reportedly creating a leftover (zombie) websocket on reconnect, with one bug report citing double responses. The other members are pull requests proposing to close the old or stale client before reconnecting; their outcome is not stated in the titles.
Open issues0
Open PRs0
Fixes on record
-
#18758 fix(discord): close old client before reconnect to prevent zombie websockets (salvage #18224)
files:
gateway/platforms/discord.py,tests/gateway/test_discord_connect.py
2 PRs closed without merging
From the close comments: merged via another change 1 · superseded by another PR 1
Closed issues · 1
- Closed#18187[Bug]: Discord adapter creates zombie websocket connection on reconnect, causing double responses
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
- Merged PRs
- #18758
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 2 May 2026