Skip to content

Conversation

Boss-1s
Copy link
Contributor

@Boss-1s Boss-1s commented Sep 26, 2025

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)

Encountering a WebSocketBadStatusException most likely means that Scratch's cloud is down. 

Signed-off-by: Boss-1s <[email protected]>
@faretek1
Copy link
Collaborator

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

Copy link
Collaborator

@faretek1 faretek1 left a 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 <[email protected]>
@Boss-1s
Copy link
Contributor Author

Boss-1s commented Sep 27, 2025

So if I did that, would we still need the message in the _base.py file?
0efb507

@faretek1
Copy link
Collaborator

faretek1 commented Sep 28, 2025

So if I did that, would we still need the message in the _base.py file?
0efb507

no. just need to check it work, and I'll merge

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.
@faretek1 faretek1 merged commit e83c63e into TimMcCool:main Sep 28, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants