Attempt a full reconnection when a resume attempt failed. #1465
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why do we need to reconnect from scratch?
It seems that a resume does not have to succeed after voice connection closes. See Discord documentation Voice#Buffered Resume
What changed?
In this change I made
discord_clientpass a callback intovoiceconnfor initiating the voice connection.voiceconnalso passes a callback into its owningdiscord_voice_clientto execute when resuming fails. This callback will makevoiceconnreinitiate the voice connection through itscreator(thediscord_client). This works even after shard reconnects.Testing
I left the bot running in a voice channel for 2 days. Verified in the log that full voice reconnection, and shard reconnection were both triggered. Finally, I joined the voice channel myself and talked, the bot still receives my voice data.
Code change checklist