-
Notifications
You must be signed in to change notification settings - Fork 881
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
Snap sync client handle empty final account storage ranges #6295
Closed
garyschulte
wants to merge
10
commits into
hyperledger:main
from
garyschulte:bugfix/snap-empty-storage-ranges
Closed
Snap sync client handle empty final account storage ranges #6295
garyschulte
wants to merge
10
commits into
hyperledger:main
from
garyschulte:bugfix/snap-empty-storage-ranges
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
|
garyschulte
force-pushed
the
bugfix/snap-empty-storage-ranges
branch
2 times, most recently
from
December 14, 2023 22:24
85cb6ab
to
73291e1
Compare
garyschulte
force-pushed
the
bugfix/snap-empty-storage-ranges
branch
from
December 18, 2023 18:10
73291e1
to
b5a594c
Compare
matkt
requested changes
Dec 20, 2023
ethereum/eth/src/main/java/org/hyperledger/besu/ethereum/eth/sync/snapsync/PersistDataStep.java
Outdated
Show resolved
Hide resolved
ethereum/eth/src/main/java/org/hyperledger/besu/ethereum/eth/sync/snapsync/RequestDataStep.java
Outdated
Show resolved
Hide resolved
ethereum/eth/src/main/java/org/hyperledger/besu/ethereum/eth/sync/snapsync/StackTrie.java
Outdated
Show resolved
Hide resolved
&& Arrays.compare(location.toArrayUnsafe(), endKeyHash.toArrayUnsafe()) <= 0; | ||
return location.isEmpty() | ||
|| (Arrays.compare(location.toArrayUnsafe(), startKeyHash.toArrayUnsafe()) >= 0 | ||
&& Arrays.compare(location.toArrayUnsafe(), endKeyHash.toArrayUnsafe()) <= 0); |
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.
👍
garyschulte
force-pushed
the
bugfix/snap-empty-storage-ranges
branch
3 times, most recently
from
January 18, 2024 18:02
7cff6d0
to
d1abab6
Compare
…as complete Signed-off-by: garyschulte <[email protected]>
Signed-off-by: garyschulte <[email protected]>
Signed-off-by: garyschulte <[email protected]>
Signed-off-by: garyschulte <[email protected]>
Signed-off-by: garyschulte <[email protected]>
Signed-off-by: garyschulte <[email protected]>
…avoid throwing MerkleTrieException for failed lookups Signed-off-by: garyschulte <[email protected]>
…roken persist test Signed-off-by: garyschulte <[email protected]>
…hen the proof is valid and empty (request was complete) Signed-off-by: garyschulte <[email protected]>
Signed-off-by: garyschulte <[email protected]>
garyschulte
force-pushed
the
bugfix/snap-empty-storage-ranges
branch
from
January 19, 2024 00:25
d1abab6
to
a35239a
Compare
superseded by #6847 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR description
Bugfix snap sync edge case. When snap syncing large contract storage, if the final requested range is empty, but there is an accompanying proof of exclusion, besu will not mark the request complete and will endlessly retry.
This PR handles this case by marking the request complete as long as there is an accompanying proof
Fixed Issue(s)