-
-
Notifications
You must be signed in to change notification settings - Fork 150
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
Ping Loop Event not getting cleared on reconnect #153
Comments
Ok, I guess that's fine, since the default state of a new Event is already "cleared()", something else about that version bump must be causing my issues. Still looking. |
Ahh, yes! Ok, figured it out: On reconnect, the The change from:
To:
Means that the second time a _ping_loop thread is created, it isn't reset. Maybe it needs:
|
Yes, I messed this up with that change. I just put a fix in master. Would you like to give it a try before I cut a new release? |
I tested the fix in my own file, so I think it's good. |
I just merged a requirements lockdown to 3.10.0 to our code, and then you fixed it! Such appreciation, much service! |
I can't quite put my finger on the exact issue, but we are getting an unexpected disconnect after a client.py reconnect because I think the ping_loop_event is no longer getting cleared with a recent code change in v3.11.0:
e38daad
Was this
self.ping_loop_event.clear()
supposed to be removed?I realize I don't have much detail in this ticket, but if I get time this week I can flush it out with more info on how to recreate.
The text was updated successfully, but these errors were encountered: