From adf07a0a8b49f407a790d16955994bb98479a8ea Mon Sep 17 00:00:00 2001 From: Alexander Hentschel Date: Wed, 28 Aug 2024 13:40:12 -0700 Subject: [PATCH] minor revision of log, to clarify the root causes behind the error --- engine/common/follower/compliance_core.go | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/engine/common/follower/compliance_core.go b/engine/common/follower/compliance_core.go index c8ebf1b7a82..fa297b13902 100644 --- a/engine/common/follower/compliance_core.go +++ b/engine/common/follower/compliance_core.go @@ -161,7 +161,11 @@ func (c *ComplianceCore) OnBlockRange(originID flow.Identifier, batch []*flow.Bl // a critical liveness assumption - see EpochCommitSafetyThreshold in protocol.Params for details. // -> In this case, it is ok for the protocol to halt. Consequently, we can just disregard // the block, which will probably lead to this node eventually halting. - log.Err(err).Msg("unable to validate proposal with view from unknown epoch") + log.Err(err).Msg( + "Unable to validate proposal with view from unknown epoch. While there is noting wrong with the node, " + + "this could be a symptom of (i) the node being severely behind, (ii) there is a byzantine proposer in " + + "the network, or (iii) there was no finalization progress for hundreds of views. This should be " + + "investigated to confirm the cause is the benign scenario (i).") return nil } return fmt.Errorf("unexpected error validating proposal: %w", err)