fix: reorg check by GetJustifiedNumberAndHash #111
Merged
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.
Description
It tried to fix: #87
Rational
GetJustifiedNumberAndHash
will callsnapshot
, which will callGetHeader
, but the current header has not been written into DB yet, so it will report error:unknown ancestor
.We can just write the header first, since it will be done no matter reorg is true or node.
And also fix a bug to get the latest inserted JustifiedNumber.
And update
params/chainspecs/rialto.json
according to the default QA config.