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 <sean@sigmaprime.io>
This commit is contained in:
parent
fe6af05bf6
commit
43ce0de73f
@ -605,7 +605,7 @@ impl<T: EthSpec> ExecutionLayer<T> {
|
|||||||
Ok(local)
|
Ok(local)
|
||||||
}
|
}
|
||||||
(Ok(None), Ok(local)) => {
|
(Ok(None), Ok(local)) => {
|
||||||
warn!(
|
info!(
|
||||||
self.log(),
|
self.log(),
|
||||||
"No payload provided by connected builder. \
|
"No payload provided by connected builder. \
|
||||||
Attempting to propose through local execution engine"
|
Attempting to propose through local execution engine"
|
||||||
|
Loading…
Reference in New Issue
Block a user