From 60df5f4ab609362711f4f518eb8f03df447bfedb Mon Sep 17 00:00:00 2001 From: Eitan Seri-Levi Date: Mon, 13 Oct 2025 20:18:50 -0700 Subject: [PATCH] Downgrade light client error logs (#8196) 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 --- beacon_node/client/src/compute_light_client_updates.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/beacon_node/client/src/compute_light_client_updates.rs b/beacon_node/client/src/compute_light_client_updates.rs index 44c3475bfe..0ef35588df 100644 --- a/beacon_node/client/src/compute_light_client_updates.rs +++ b/beacon_node/client/src/compute_light_client_updates.rs @@ -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( 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 };