Skip to content
Snippets Groups Projects
Unverified Commit a0fc3b54 authored by Bastian Köcher's avatar Bastian Köcher Committed by GitHub
Browse files

rpc2: Finalized event doesn't indicate that the best block changes (#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.
parent 63e26444
Branches
No related merge requests found
Pipeline #482297 waiting for manual action with stages
in 30 minutes and 44 seconds
......@@ -32,7 +32,7 @@ use futures::{
};
use futures_util::future::Either;
use jsonrpsee::SubscriptionSink;
use log::{debug, error};
use log::debug;
use sc_client_api::{
Backend, BlockBackend, BlockImportNotification, BlockchainEvents, FinalityNotification,
};
......@@ -572,7 +572,7 @@ where
// The information from `.info()` is updated from the DB as the last
// step of the finalization and it should be up to date.
// If the info is outdated, there is nothing the RPC can do for now.
error!(
debug!(
target: LOG_TARGET,
"[follow][id={:?}] Client does not contain different best block",
self.sub_id,
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment