From 43ce0de73f992d0f184c722e58ab203b7086fead Mon Sep 17 00:00:00 2001 From: realbigsean Date: Wed, 3 Aug 2022 17:13:15 +0000 Subject: [PATCH] Downgrade log for 204 from builder (#3411) ## Issue Addressed A 204 from the connected builder just indicates there's no payload available from the builder, not that there's an issue. So I don't actually think this should be a warn. During the merge transition when we are pre-finalization a 204 will actually be expected. And maybe even longer if the relay chooses to delay providing payloads for a longer period post-merge. Co-authored-by: realbigsean --- beacon_node/execution_layer/src/lib.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/beacon_node/execution_layer/src/lib.rs b/beacon_node/execution_layer/src/lib.rs index aea952a57..59c8f009f 100644 --- a/beacon_node/execution_layer/src/lib.rs +++ b/beacon_node/execution_layer/src/lib.rs @@ -605,7 +605,7 @@ impl ExecutionLayer { Ok(local) } (Ok(None), Ok(local)) => { - warn!( + info!( self.log(), "No payload provided by connected builder. \ Attempting to propose through local execution engine"