-
Notifications
You must be signed in to change notification settings - Fork 53
Open
Description
I updated Lavalink-Client from a very old version to discover that websocket connections to Lavalink would randomly break at fairly high frequency. The WS client doesn't appear to have been updated.
The server logs Error several times, but doesn't log the actual exception despite it being provided to the logger. That's really odd.
I am now using the workaround-ws-closing branch in production where this still works. Any info about this issue is greatly appreciated.
Metadata
Metadata
Assignees
Labels
No labels