[issue33093] Fatal error on SSL transport

Ned Deily added the comment: Thanks for the report and for the analysis! Closing as duplicate. -- nosy: +ned.deily resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Skip sending/receiving after SSL transport closing

[issue33093] Fatal error on SSL transport

Change by ppperry : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list

[issue33093] Fatal error on SSL transport

Eric Toombs added the comment: Well, that looks good! Looking forward to 3.6.5! -- ___ Python tracker ___

[issue33093] Fatal error on SSL transport

kyuupichan added the comment: Looks like https://bugs.python.org/issue33037 -- nosy: +kyuupichan ___ Python tracker ___

[issue33093] Fatal error on SSL transport

Matt Eaton added the comment: Eric, what is needed to try and reproduce this issue accurately? Would it be installing websockets and setting up your client to ping to the server forever (12 hours in this case)? If you are able to provide a client I would be willing

[issue33093] Fatal error on SSL transport

New submission from Eric Toombs : I'm not exactly sure what caused this error, but I was a client receiving messages on a websocket for a while (about 12 hours). Suddenly all incoming data stopped, then nothing happened for about 5 hours. Finally, I received a