Lavalink Server does not acknowledge that the voice websocket is closed when a shard is disconnected
See original GitHub issueIssue:
Lavalink Server does not acknowledge when the voice websocket is closed due to a shard being disconnected. It also does not send a WebSocketClosedEvent
, which is how I discovered this issue.
Steps to reproduce:
- Join the bot into a voice channel
- Kill the bot’s discord connection, whilst keeping the Lavalink socket open
- Notice the bot has been removed from the voice channel
- Notice nothing in the Lavalink Server logs and no events sent to the Lavalink Client
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:12 (11 by maintainers)
Top Results From Across the Web
[WIP] AutoShardedClient redesign #2654 - Rapptz/discord.py
I discovered this issue with the latest build of the shard-rework branch. When i disconnect my bt from the voice channel, the console...
Read more >Red-Lavalink 0.11.0rc1 documentation
Raises ------ IndexError If there are no available lavalink nodes ready to connect to discord. """ node_ = node.get_node(channel.guild.id) p = await ...
Read more >What does "WebSocket is closed before the connection is ...
I have done a search through my entire project directory and found no instance of ws.close() . Am I missing something? – Kendall...
Read more >API Reference - nextcord
The websocket gateway the client is currently connected to. Could be None . The event loop that the client uses for asynchronous operations....
Read more >API 레퍼런스 - discord.py
When the client logs on and connects to the websocket, Discord does not provide ... region ( VoiceRegion ) – The region for...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the headsup @MinnDevelopment. As I mentioned in the JDA server the other day I was a total idiot about the Java 8 Magma thing. We should discuss getting all the stuff into a single repo, please contact me on Discord if you have interest and time.
@napstr the documentation is wrong.