gnosis/lighthouse
1
0
Fork 0
mirror of https://github.com/sigp/lighthouse.git synced 2026-03-14 18:32:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

Downgrade light client error logs (#8196)

Browse Source 
Temporary stop gap for #7002


  Downgrade light client errors to debug

We eventually should fix our light client objects so they can consist of data across forks.


Co-Authored-By: Eitan Seri- Levi <eserilev@gmail.com>
This commit is contained in:
Eitan Seri-Levi
2025-10-13 20:18:50 -07:00
committed by GitHub
parent 1fb94ce432
commit 60df5f4ab6
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
beacon_node/client/src/compute_light_client_updates.rs
View File

@@ -3,7 +3,7 @@ use beacon_processor::work_reprocessing_queue::ReprocessQueueMessage;
use beacon_processor::{BeaconProcessorSend, Work, WorkEvent};
use futures::StreamExt;
use futures::channel::mpsc::Receiver;
use tracing::error;
use tracing::{debug, error};
// Each `LightClientProducerEvent` is ~200 bytes. With the light_client server producing only recent
// updates it is okay to drop some events in case of overloading. In normal network conditions
@@ -27,7 +27,7 @@ pub async fn compute_light_client_updates<T: BeaconChainTypes>(
chain
.recompute_and_cache_light_client_updates(event)
.unwrap_or_else(|e| {
error!("error computing light_client updates {:?}", e);
debug!("error computing light_client updates {:?}", e);
});
let msg = ReprocessQueueMessage::NewLightClientOptimisticUpdate { parent_root };