Open
Description
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)