-
Notifications
You must be signed in to change notification settings - Fork 3
357/359/377 - bug fixes #370
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
Conversation
} | ||
} else { | ||
forkBlocks = append(forkBlocks, block) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should there be special handle once notice fork block is pushed? I mean if we already notice a single fork block, that mean we won't be able to validate the rest of the block anymore right? but this is just an open question, I'm not sure about the overall implementation regarding the fork process.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice catch! I have handled it by breaking from the loop. Thank you
please fix the tests, and update base branch. @capt4ce |
@andy-shi88 Just fixed the failed CI. Please kindly check it again |
Description
Fix bug fixes related to download blockchain and rollback
Breakdown
Reference Issue
Close #359 #357 #377
Step to Test (optional)