Skip to content

Conversation

justinpolygon
Copy link
Collaborator

This PR upgrades the WebSocket client to use websockets 14+ by switching to the new asyncio implementation (websockets.asyncio.client), updating type hints to ClientConnection, and adding process_exception=lambda exc: None to mimic legacy reconnection behavior on any error. It also fixes #818 by propagating ConnectionClosedError after exceeding max_reconnects, improving error handling without breaking user scripts. Requires Python 3.9+. Tested for compatibility; no end-user API changes.

@justinpolygon
Copy link
Collaborator Author

justinpolygon commented Oct 15, 2025

This is failing since 3.8 is not supported anymore. We need to update the github action. So, I'll re-test this once we fix #936.

@penelopus
Copy link

i approved this before noticing that the test for 3.8 is failing — can you take a look at that?

@justinpolygon justinpolygon merged commit 153f4ea into master Oct 15, 2025
9 checks passed
@justinpolygon justinpolygon deleted the feat/upgrade-websockets-14-fix-reconnect-error branch October 15, 2025 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

WebSocketClient should propagate ConnectionClosedError after max_reconnects

2 participants