You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When testing flask-sock, I ran into an issue where I wasn't getting a ConnectionClosed exception when the client closes the connection (using None timeout). In fact, as it appears that as self.connected is not being toggled, the resulting behavior is that the loop is entered for one more iteration, and my server hangs indefinitely attempting to receive.
I traced it here. Adding a sleep before the event clear makes it work properly, but is obviously a hack.
Edit: It appears that just using a timeout solves the problem. However, you might still want to look at this so I'll keep everything up.
The text was updated successfully, but these errors were encountered:
@bxdn I'm unable to reproduce this race condition here, but I think I have found the problem anyway. Can I ask you to install the main branch of this package and retest? Thanks!
When testing flask-sock, I ran into an issue where I wasn't getting a ConnectionClosed exception when the client closes the connection (using None timeout). In fact, as it appears that as self.connected is not being toggled, the resulting behavior is that the loop is entered for one more iteration, and my server hangs indefinitely attempting to receive.
I traced it here. Adding a sleep before the event clear makes it work properly, but is obviously a hack.
Edit: It appears that just using a timeout solves the problem. However, you might still want to look at this so I'll keep everything up.
The text was updated successfully, but these errors were encountered: