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
{{ message }}
This repository has been archived by the owner on Apr 29, 2022. It is now read-only.
If a KeyError is thrown in the handler, it will be caught and no log output will be produced. It bit me and it took some time to figure out what was happening.
Proposed fix: try-except-KeyError only the environ lookup.
@lenolib I know this is a very old issue, but thank you for pointing me in the right direction after a frustrating hour of debugging a flask-sockets application that would sometimes drop connections completely silently with no error output from Gunicorn.
The culprit was a KeyError in the socket handler, and as noted above KeyErrors are silently absorbed by the library. The solution suggestion above works for me as well.
If a KeyError is thrown in the handler, it will be caught and no log output will be produced. It bit me and it took some time to figure out what was happening.
Proposed fix: try-except-KeyError only the
environ
lookup.https://github.com/kennethreitz/flask-sockets/blob/master/flask_sockets.py#L47
The text was updated successfully, but these errors were encountered: