This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Fix syncing logic for reverting - Closes #4103 #4104
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4miners
previously requested changes
Aug 16, 2019
ishantiw
approved these changes
Aug 16, 2019
…sk-sdk into 4103-fix_syncing_logic
ManuGowda
approved these changes
Aug 16, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was the problem?
When the chain is on fork, it doesn't rollback if it fails to fetch block from network, instead it rolls back when it fails to process
How did I solve it?
Move the logic to the network fail.
How to manually test it?
Build some blockchain data (around height 100), and connect to different network.
Review checklist