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
I don't think we even want to swallow the reconnection-specific errors. Should the condition be completely removed?
The text was updated successfully, but these errors were encountered:
jeanbmar
changed the title
on_error callback stop being called after first reconnection
on_error callback stops being called after first reconnection
Feb 18, 2024
After a failure, this line will set the WebSocketApp instance in reconnecting mode forever:
https://github.com/websocket-client/websocket-client/blob/master/websocket/_app.py#L613
Indeed,
setSock
will only be called as reconnecting. As a result any further error will be swallowed here:https://github.com/websocket-client/websocket-client/blob/master/websocket/_app.py#L582
I don't think we even want to swallow the reconnection-specific errors. Should the condition be completely removed?
The text was updated successfully, but these errors were encountered: