Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not fail production when consensus block value is unavailable #14111

Merged
merged 4 commits into from
Jun 14, 2024

Conversation

rkapka
Copy link
Contributor

@rkapka rkapka commented Jun 14, 2024

What type of PR is this?

Other

What does this PR do? Why is it needed?

We sometimes see sync committee signature verification failures when trying to get sync committee rewards for a given block. The reason for this bug is still unknown, but failing block production because of such a non-critical thing is too radical.

Which issues(s) does this PR fix?

Fixes #13910

Other notes for review

I modified the comment for Phase 0 to explain why we ignore it.

@rkapka rkapka added Ready For Review A pull request ready for code review API Api related tasks labels Jun 14, 2024
@rkapka rkapka requested a review from a team as a code owner June 14, 2024 14:27
@@ -297,8 +297,8 @@ func getConsensusBlockValue(ctx context.Context, blockRewardsFetcher rewards.Blo
}
}
if bb.Version() == version.Phase0 {
// ignore for phase 0
return "", nil
// Getting the block value for Phase 0 is very hard, so we ignore it
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we at least add a debug log or something

@@ -220,8 +220,8 @@ func (s *Server) produceBlockV3(ctx context.Context, w http.ResponseWriter, r *h

consensusBlockValue, httpError := getConsensusBlockValue(ctx, s.BlockRewardFetcher, v1alpha1resp.Block)
if httpError != nil {
httputil.WriteError(w, httpError)
return
// Having the consensus block value is not critical to block production
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should warn or add something in the header maybe?

@rkapka rkapka enabled auto-merge June 14, 2024 15:02
@rkapka rkapka added this pull request to the merge queue Jun 14, 2024
Merged via the queue into develop with commit 17561a6 Jun 14, 2024
16 of 17 checks passed
@rkapka rkapka deleted the sync-rewards-fail branch June 14, 2024 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Api related tasks Ready For Review A pull request ready for code review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Could not get sync aggregate rewards
4 participants