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

[Bug] When using --connect, if we lose the connection it may not reconnect, ever #366

Open
Davidson-Souza opened this issue Feb 4, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@Davidson-Souza
Copy link
Collaborator

Davidson-Souza commented Feb 4, 2025

Describe the bug
When running florestad with --connect=<ip>, if some transient network error happens (e.g. your wifi connection dies). florestad may get stuck, even after the network comes back up. This seems to only happen when we are on the SyncNode phase.

Steps to Reproduce
Start florestad with --connect=IP
Wait until it downloads all headers
Once it gets to the sync phase, kill your network
Wait a few minutes
Connect with the network again

Expected behavior
It should re-connect with that peer and continue the process

Build environment
version 0.7.0-40-gf7bbd0e compiled for x86_64-linux-gnu with rustc 1.74.1 (a28077b28 2023-12-04)

@Davidson-Souza Davidson-Souza added the bug Something isn't working label Feb 4, 2025
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