Skip to content
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

Websocket clients do not automatically reconnect on dropped connection #7

Open
minicheddar opened this issue Jan 3, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@minicheddar
Copy link
Owner

Whilst ping/pongs are handled per exchange task, if a websocket connection is dropped it does not automatically reconnect.

Add support for automatic reconnect with exponential back-off (to avoid rate limiting)

@minicheddar minicheddar added the bug Something isn't working label Jan 3, 2023
@minicheddar minicheddar changed the title Websocket connection does not automatically reconnect on dropped connection Websocket clients do not automatically reconnect on dropped connection Jan 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant