You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: