-
Notifications
You must be signed in to change notification settings - Fork 700
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
chainHead/follow: Provide multiple block hashes to the initialized event #3445
Merged
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
21f0661
chainHead: Extend `Initialized` event to support multiple hashes
lexnv 2c33377
chainHead: Provide more finalized blocks in the initial event
lexnv 4869964
chainHead: Handle pinning during block collection
lexnv 2b4f2fd
chainHead/events: Adjust test events
lexnv 543bc92
chainHead/tests: Adjust test to include multiple hashes
lexnv 7b66662
chainHead/tests: Apply rustfmt
lexnv c993cec
Update substrate/client/rpc-spec-v2/src/chain_head/chain_head_follow.rs
lexnv 3960b27
Update substrate/client/rpc-spec-v2/src/chain_head/chain_head_follow.rs
lexnv fd877ed
Update substrate/client/rpc-spec-v2/src/chain_head/chain_head_follow.rs
lexnv c8ff561
Update substrate/client/rpc-spec-v2/src/chain_head/chain_head_follow.rs
niklasad1 3aa6c60
Merge remote-tracking branch 'origin/master' into lexnv/multiple-chai…
lexnv cbeecb2
chainHead: Replace zip with manual parent iter
lexnv 626a33a
Merge branch 'master' into lexnv/multiple-chain-head-event
lexnv 1989d41
Merge branch 'master' into lexnv/multiple-chain-head-event
lexnv 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 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 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 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.
Not a comment related to this PR, but could we do some kind of sanity check of the distance between leaf and finalized block? This code assumes that they are close together, as they should be. However, on parachains for example, the finalization of para blocks is dependent on the relay chain.
If the embedded relay chain node syncs slower while the parachain node is already at the tip, between a leaf and the known finalized block could be millions of blocks (until relay chain has caught up).
This would lead to:
Maybe we should add some kind of safeguard against such situations.
Certainly an edge case however.
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.
Have create this PR to handle that edge-case: #3562 🙏