Exception for WebSocketClosedEvent

[csuvajit]

No description provided.

[appellation]

This should probably be handled more gracefully, since many of those events are recoverable simply by reconnecting. I'm not sure if Lavalink does anything on its end to handle that, but if not it's definitely something we can do on the client library side to make the developer experience much nicer.

[ridays2001]

I think Lavalink does it because the people using the original Java version don't experience this problem.

[appellation]

I think Lavalink does it because the people using the original Java version don't experience this problem.

Does this mean that Lavalink only forwards unrecoverable close codes? The Lavalink documentation on this subject is a bit sparse, and it's hard for me to test personally since I no longer use it; however, the implication here is that it sends any and all voice websocket close events.

[csuvajit]

I should have explained! This is not about close code.
If we kick the bot from voice channel, lavalink emits WebSocketClosedEvent event which skips the currently playing song.
A month ago @ridays2001 shared this issue in Lavalibs server.

[ridays2001]

And the song keeps on playing even when it's supposed to be paused. I didn't notice it before. But, after some debugging, I found that out. Once the bot leaves the VC, even if the song was paused, it automatically resumes the song in the background... @csuvajit told me that this WebSocketClosed caused the problem...

[ridays2001]

But, when I asked around in the JDA server, I found out that people using original Java client don't experience this issue... That's why I thought that it's fixed in Lavalink

[appellation]

Ah, sure, that makes sense. Thank you for clarifying.