Discord liveness watchdog socket-closed strike fixes
Cluster 118487. Data as of
Nothing open on GitHub. Fix merged in #118919 on 22 Sep 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 #118919. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #118919. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests address bugs in the Discord liveness watchdog where a socket_closed strike could cause the watchdog to stop functioning silently, fail to escalate, or fail to trigger a reconnect. The work focuses on improving strike handling and reconnection behavior.
Open issues0
Open PRs0
Fixes on record
-
#118919 fix(discord): reconnect on the first closed-transport liveness sample
files:
contributors/emails/[email protected],plugins/platforms/discord/adapter.py,tests/gateway/test_discord_liveness.py,website/docs/reference/environment-variables.md,website/docs/user-guide/messaging/discord.md
2 PRs closed without merging
From the close comments: merged via another change 1 · superseded by another PR 1
Closed issues · 1
- Closed#118487[Bug]: Discord liveness watchdog dies after first socket_closed strike (1/2) — adapter zombie, no reconnect, no fatal
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
- #118919
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 22 Sep 2026