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] Guard recursive certificate fetching with is_synced check. #3256

Merged
merged 11 commits into from
May 23, 2024

Conversation

raychu86
Copy link
Contributor

Motivation

This PR prevents nodes from recursively fetching missing certificates, despite syncing via blocks. This should not happen, and the node should focus on syncing via the blocks.

We noticed this edge case where a node would be considered synced for a moment and then start fetching certificates from peers. This cycle can go on for a long time since there may be many certificates to request, however this should be cut short when the node realizes that it should be syncing via blocks instead.

Copy link
Contributor

@vicsn vicsn left a comment

Choose a reason for hiding this comment

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

Changes make sense to me - and it passed yesterday's automated e2e test run which includes syncing.

@howardwu howardwu merged commit b55162b into mainnet-staging May 23, 2024
0 of 24 checks passed
@howardwu howardwu deleted the fix/is-syncing-check branch May 23, 2024 22:29
zosorock added a commit that referenced this pull request May 24, 2024
This reverts commit b55162b, reversing
changes made to 7ff06a8.
vicsn added a commit to ProvableHQ/snarkOS that referenced this pull request May 28, 2024
joske pushed a commit to eqlabs/snarkOS that referenced this pull request May 29, 2024
…heck"

This reverts commit b55162b, reversing
changes made to 7ff06a8.
vicsn added a commit to ProvableHQ/snarkOS that referenced this pull request Jun 6, 2024
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.

4 participants