-
Notifications
You must be signed in to change notification settings - Fork 839
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 snapsync issue with forest #5776
Conversation
Signed-off-by: Karim TAAM <karim.t2am@gmail.com>
|
Signed-off-by: Karim TAAM <karim.t2am@gmail.com>
Tests done
|
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.
LGTM this fix the sync on the Sepolia instance, just a style suggestion.
public Optional<Bytes> getUnSafeTrieNode(final Bytes key) { | ||
return keyValueStorage.get(key.toArrayUnsafe()).map(Bytes::wrap); | ||
} |
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.
a style suggestion, rename method to getTrieNodeUnsafe
to uniform with other unsafe methods like toArrayUnsafe
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.
done
Signed-off-by: Karim TAAM <karim.t2am@gmail.com>
Fixing an issue during snapsync with forest related to the heal step Signed-off-by: Karim TAAM <karim.t2am@gmail.com>
Fixing an issue during snapsync with forest related to the heal step Signed-off-by: Karim TAAM <karim.t2am@gmail.com>
Fixing an issue during snapsync with forest related to the heal step Signed-off-by: Karim TAAM <karim.t2am@gmail.com> Signed-off-by: garyschulte <garyschulte@gmail.com>
Fixing an issue during snapsync with forest related to the heal step Signed-off-by: Karim TAAM <karim.t2am@gmail.com>
PR description
Fixing an issue during snapsync with forest related to the heal step
the step checking whether the node existed or not during the healing process could lead to a null pointer exception due to the null nodeHash, which was only utilized within the context of forest.
Fixed Issue(s)