Open muddyfish opened 7 years ago
Can your reproduce the error now? Chat often has some outtakes and especially this lib has it's issues with it. I'd suggest to wrap the watch()
or the watch_socket()
function in a try ... except
and catch any exceptions you may receive. That should also eliminate crashes when the socket connection dies.
Also, 500 Error codes mostly suggest it's an issue on SE's side (since HTTP errors in the 500 range are server errors)
When receiving messages from SE, it raised a 500 error. After this, it no longer read any more messages. This is probably due to the exception killing off the reader