You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the scenario where a websocket connection is closed before being accepted by the server, the WebSocketSession currently throws an AssertionError due to the received message not being type "websocket.accept" (see assertion)
If a connection request is cancelled before being accepted it should raise the message in someway so tests can process the response.
This should also apply to any message being received first that isn't an accept type since any of these would be a failure of the websocket protocol
The text was updated successfully, but these errors were encountered:
In the scenario where a websocket connection is closed before being accepted by the server, the WebSocketSession currently throws an
AssertionError
due to the received message not being type"websocket.accept"
(see assertion)If a connection request is cancelled before being accepted it should raise the message in someway so tests can process the response.
This should also apply to any message being received first that isn't an accept type since any of these would be a failure of the websocket protocol
The text was updated successfully, but these errors were encountered: