-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BrokenPipeError in _thread #29
Comments
Yes, good catch on this, the call to |
If it helps, this is our current workaround
|
@sanchay-hai Can I ask you to install the main branch of this package and confirm that there are no more issues with broken pipe errors in the background thread? Once you report success I'll issue a new release. Thanks. |
Thank you! will try it out when I get the chance |
Hello,
We occasionally get BrokenPipeErrors from
_thread
which kills our server. Here is the stack trace:Not sure if there's anything we can do on the client side to handle this as it is happening in a thread not in our control. Maybe you need a try / catch in the thread so the thread doesn't die?
Related note, could you perhaps name the thread, right now it shows up as
_thread
, not the most descriptive name.We're using
simple-websocket==0.10.1
Thanks!
The text was updated successfully, but these errors were encountered: