-
Notifications
You must be signed in to change notification settings - Fork 51
Add note when encountering WebSocketBadStatusException #490
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
Conversation
Encountering a WebSocketBadStatusException most likely means that Scratch's cloud is down. Signed-off-by: Boss-1s <95505913+Boss-1s@users.noreply.github.com>
maybe add a note suggesting to try using tw Cloud. If the websocket error occurs when using tw cloud, then don't send the message |
Signed-off-by: retek <107722825+faretek1@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there should be a check that we only show this message when it's a scratch cloud. If it's turbowarp cloud, just let the error exist.
Signed-off-by: Boss-1s <95505913+Boss-1s@users.noreply.github.com>
So if I did that, would we still need the message in the _base.py file? |
no. just need to check it work, and I'll merge |
Signed-off-by: TheCommCraft <79996518+TheCommCraft@users.noreply.github.com>
It seems like the scratch cloud variables are up again, so it can't really be tested anymore. On that note, we should test if new scratchers and banned accounts can still set cloud vars.
Encountering a WebSocketBadStatusException most likely means that Scratch's cloud is down, thus I have added a little note when a WebSocketBadStatusException is encountered when attempting to establish a WebSocket connection.
This could be improved on, I may make more edits later.
#487 (comment)
(Ignore failed workflow runs)