trio-websocket icon indicating copy to clipboard operation
trio-websocket copied to clipboard

Published 20 hours ago • verified publisher icon python-trio

Debugging connection closed on 1006

Open nicknotfun opened this issue 3 years ago • 2 comments

I've got a client of an internal tool who runs into ABNORMAL_CLOSURE / code=1006; and it's providing difficult to reproduce other than on his machine.

The debug log pattern is:

  1. Connect to websocket
  2. Log prints "sending 322 bytes"
  3. Connection closed
  4. Reader task finished.

I'll continue to investigate, but it would be very useful if we could eliminate any reason-lacking 1006 codes; for example knowing if it's a broken resource error vs. a client bug.

nicknotfun avatar Oct 21 '21 18:10 nicknotfun