-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[stable2509] Backport #10525 #10555
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
Merged
+137
−9
Merged
[stable2509] Backport #10525 #10555
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
c37a4f5
fix(rpc-spec-v2): best block not announced immediately after initiali…
voliva c566dd5
Merge branch 'stable2509' into backport-10525-to-stable2509
EgorPopelyaev 992ba68
Apply suggestions from code review
lexnv 0278074
Merge branch 'stable2509' into backport-10525-to-stable2509
EgorPopelyaev 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,30 @@ | ||
| title: 'fix(rpc-spec-v2): best block not announced immediately after initialised' | ||
| doc: | ||
| - audience: Node Dev | ||
| description: |- | ||
| # Description | ||
|
|
||
| Fixes https://github.com/polkadot-api/polkadot-api/issues/1244 | ||
|
|
||
| The current chainHead_v1 implementation is [not spec-compliant](https://paritytech.github.io/json-rpc-interface-spec/api/chainHead_v1_follow.html), as it states: | ||
|
|
||
| > - Generates an `initialized` notification | ||
| > - Generates one `newBlock` notification for each non-finalized block | ||
| > - Then a `bestBlockChanged` notification | ||
| > - When a new block arrives, generates a `newBlock` notification | ||
| > - When the node finalizes a block, generates a `finalized` notification | ||
|
|
||
| And the current implemention only emits the `bestBlockChanged` notification after initialized iif the best block is different from the finalized block. | ||
|
|
||
| PAPI recently is using this part of the spec as an assumption. Most chains are unaffected, but those that produce blocks on-demand (e.g. manual-seal) then have polkadot-api hanging until there's a higher block different than the finalized one. | ||
|
|
||
| ## Integration | ||
|
|
||
| This PR doesn't change any of the APIs of the node. Upgrade should be automatic. | ||
|
|
||
| ## Review Notes | ||
|
|
||
| This PR removes that condition so that the `bestBlockChanged` notification is always emited. All tests are updated to this new behaviour | ||
| crates: | ||
| - name: sc-rpc-spec-v2 | ||
| bump: major | ||
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.
Uh oh!
There was an error while loading. Please reload this page.