Discord voice credentials stale after DAVE re-key
Cluster 77968 · gateway. Data as of
Nothing open on GitHub. Fix merged in #131833 on 5 Oct 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 #131833. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #131833. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where Discord voice receiver credentials are captured once at startup and not updated when DAVE re-keys or voice reconnects occur. Fixes involve tracking live credentials dynamically rather than snapshotting them at start().
Open issues0
Open PRs0
Fixes on record
-
#131833 fix(discord): track live voice credentials across re-keys instead of snapshotting at start() [risk 0.30]
files:
plugins/platforms/discord/adapter.py,tests/gateway/test_discord_voice_rekey.py
2 PRs closed without merging
From the close comments: superseded by another PR 1 · other 1
Closed issues · 1
- Closed#77968Discord voice receiver goes silently deaf after a DAVE re-key or voice reconnect — credentials are snapshotted once at start()
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
- Subsystem
- gateway
- Merged PRs
- #131833
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 5 Oct 2026