Closed mad-moo closed 3 months ago
This sounds similar to a bug I wrestled with when I refactored the Transport
code. FastAPI websockets become unusable when the _serve_websocket
function exits, but aren't closed. Maybe the websocket is entering its "unusable" state for some reason.
Describe the bug
After having Rio apps open for a while they will often quietly disconnect. There is no indication of this - connection lost popup doesn't show - but the app no longer responds to any user input.
Expected Behavior
Either don't lose connection at all, or transparently re-establish one.
Steps to Reproduce
Screenshots/Videos
No response
Operating System
Windows, Linux
What browsers are you seeing the problem on?
Chrome, Firefox
Browser version
No response
What device are you using?
Desktop, Mobile
Additional context
No response