-
Notifications
You must be signed in to change notification settings - Fork 1.2k
remote-ext: fix silent state corruption from lagging RPC providers #12268
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
Open
Stephenlawrence00
wants to merge
4
commits into
paritytech:master
Choose a base branch
from
Stephenlawrence00:remote-ext-fix
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+176
−5
Open
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
9acab05
remote-ext: fix silent state corruption from lagging RPC providers
Stephenlawrence00 d157f78
Update from github-actions[bot] running command 'prdoc --audience nod…
github-actions[bot] 73031e7
remote-ext: fix silent state corruption from lagging RPC providers
Stephenlawrence00 5932090
apply changes
Stephenlawrence00 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| title: 'remote-ext: fix silent state corruption from lagging RPC providers' | ||
| doc: | ||
| - audience: Node Dev | ||
| description: "Fixes #12264 by treating per-item RPC errors as batch failures instead\ | ||
| \ of empty values, verifying the computed storage root against the block header\ | ||
| \ before caching a snapshot, and excluding RPC providers that lack the target\ | ||
| \ block up front.\r\n" | ||
| crates: | ||
| - name: frame-remote-externalities | ||
| bump: patch |
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
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.
Will this also work for child tries?
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.
Yes. With
child_trieon, a complete scrape pulls every child trie (load_child_remote) and inserts it viainsert_child.into_raw_snapshotrecomputes each child root and folds it into the top trie, so the computed_root we compare to the header'sstate_rootalready covers child data. A stale child trie changes the top root and fails the check.