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
AFAICS this behavior is caused by runWebSocketsWith re-throwing iteratee exceptions. runWebSocketsSnapWith does not handle this, hence the exception reaches Snap. How about:
Given this test server:
and this example client.
Starting the server and the client establishes the connection just fine, but when the client receives a
SIGINT
the server logs:an exception escaped to toplevel:
ParseError {errorContexts = ["demandInput"], errorMessage = "not enough bytes"}
This happens only before the client has sent any data messages.
The text was updated successfully, but these errors were encountered: