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
Ideally, the websocket could be closed both explicitly, with a client.close() method, and implicitly when the client goes out of scope.
The current implementation causes an issue in jest integration tests where a test that uses WebsocketTransport will hang forever, or until the websocket times out, and there is no way to close the socket, since the client.transport.ws field is private.
The text was updated successfully, but these errors were encountered:
Ideally, the websocket could be closed both explicitly, with a
client.close()
method, and implicitly when the client goes out of scope.The current implementation causes an issue in jest integration tests where a test that uses WebsocketTransport will hang forever, or until the websocket times out, and there is no way to close the socket, since the
client.transport.ws
field is private.The text was updated successfully, but these errors were encountered: