Replace closeConnection with shutdownRuntime and disconnectWebsocket #5809
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📚 Context
This is another change that's being made because we need it for the
feature/session-managerbranchbut is being made straight to
developto keep the final diff size down.The special test-only
closeConnectionproto message type has a pretty misleading name because whatit really does is shut down the runtime entirely. Because we need a way to test reconnect behavior (and thus
a way to close only the browser websocket connection without nuking the entire Streamlit server), we replace
this proto type with
debugShutdownRuntimeanddebugDisconnectWebsocket, which do what their namessuggest.
🧪 Testing Done