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

fix: snap synchronization failed #60

Merged
merged 2 commits into from
Nov 7, 2023
Merged

fix: snap synchronization failed #60

merged 2 commits into from
Nov 7, 2023

Conversation

0xcb9ff9
Copy link

@0xcb9ff9 0xcb9ff9 commented Nov 6, 2023

Description

Fix: #56

PR #31 misunderstood the synchronization logic. In the state of snapshot synchronization, the height of the peer block should be much higher than the local, the node should not be disconnected.

Copy link
Collaborator

@DarianShawn DarianShawn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I totally agree that node should not break connection during syncing.

@DarianShawn DarianShawn added this pull request to the merge queue Nov 7, 2023
Merged via the queue into dev with commit c094025 Nov 7, 2023
4 of 5 checks passed
@DarianShawn DarianShawn deleted the fix-snap-sync branch November 7, 2023 04:23
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.

my mainnet node is not syncing is showing looking for peers
2 participants