Do not suggest to "Fix beacon client" after CL inactivity #7355
Labels
A-consensus
Related to the consensus engine
A-observability
Related to tracing, metrics, logs and other observability tools
C-bug
An unexpected or incorrect behavior
M-prevent-stale
Prevents old inactive issues/PRs from being closed due to inactivity
Inspired by this issue: #7353
The "Fix your beacon client" suggestion is both inaccurate and not useful, as reth may have been the one to return an error. While this log has been useful in response to users who don't know they need a CL, we should provide accurate information, especially if reth returned an invalid block error. We could also point users to the debug log directory to send to us in a bug report.
We cannot distinguish between "true" invalid blocks and blocks we mark as invalid due to an error in reth until we have hindsight w.r.t. a specific bug, so we should be careful in our wording
The text was updated successfully, but these errors were encountered: