Skip to content

Fall hub connections back to non-websocket transports if websocket persistently fails#36617

Draft
bdach wants to merge 4 commits intoppy:masterfrom
bdach:fallback-to-non-websocket
Draft

Fall hub connections back to non-websocket transports if websocket persistently fails#36617
bdach wants to merge 4 commits intoppy:masterfrom
bdach:fallback-to-non-websocket

Conversation

@bdach
Copy link
Collaborator

@bdach bdach commented Feb 7, 2026

In a theoretical scenario wherein client & server go through transport negotiation, agree to use websockets, but then websockets get killed persistently but other transports might not be getting killed persistently, this theoretically maybe allows said users to connect to spectator server.

I've only vaguely tested that this vaguely does what I wrote above. I don't know whether this diff is going to help a single user. Would need users currently affected by spectator server blocks to test and say.

@bdach bdach self-assigned this Feb 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant