Skip to content
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

rpc2: Finalized event doesn't indicate that the best block changes #4872

Merged
merged 2 commits into from
Jun 25, 2024

Conversation

bkchr
Copy link
Member

@bkchr bkchr commented Jun 24, 2024

We should not print a warning if the best block stays the same between two finality events. There is no requirement that this changes. For sure this doesn't need to be an error message.

We should not print a warning if the best block stays the same between
two finality events. There is no requirement that this changes. For sure
this doesn't need to be an error message.
@bkchr bkchr added the R0-silent Changes should not be mentioned in any release notes label Jun 24, 2024
@bkchr bkchr requested review from lexnv and a team June 24, 2024 18:11
@paritytech-cicd-pr
Copy link

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-clippy
Logs: https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/6535062

@bkchr bkchr enabled auto-merge June 25, 2024 07:30
@bkchr bkchr added this pull request to the merge queue Jun 25, 2024
Merged via the queue into master with commit a0fc3b5 Jun 25, 2024
159 of 160 checks passed
@bkchr bkchr deleted the bkchr-rpc2-fix branch June 25, 2024 09:01
TarekkMA pushed a commit to moonbeam-foundation/polkadot-sdk that referenced this pull request Aug 2, 2024
…aritytech#4872)

We should not print a warning if the best block stays the same between
two finality events. There is no requirement that this changes. For sure
this doesn't need to be an error message.
sfffaaa pushed a commit to peaqnetwork/polkadot-sdk that referenced this pull request Dec 27, 2024
…aritytech#4872)

We should not print a warning if the best block stays the same between
two finality events. There is no requirement that this changes. For sure
this doesn't need to be an error message.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R0-silent Changes should not be mentioned in any release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants