-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panic when connecting to old servers (or WebTransports) #193
Comments
As a note on a possible option to have a handle in the future. There could be a global |
@philippseith this is a bit urgent because as I wrote this brings the process down at the moment. So either merge #192 and I rebase #191 on it or merge #191 directly and get user feedback on potential bugs. At the moment I have a local replace directive on #192 which seems to not always work and when it falls back to current master it crashes my process as described in the OP |
|
When hitting a server which reports that it wants to use WebTransports signalR brings down the whole process due to a programming error. This error can't be gracefully handled as it is a panic within a Goroutine singalR spawns.
Edit: the stack above came actually when trying to connect to a old server. However in both cases the panic is the same
The text was updated successfully, but these errors were encountered: