-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Return errors from ProduceBlindedBlock
#12309
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add some tests to cover these new additions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is correct, the beacon api stated the return should be blinded block or error. In this case, wouldn't error be most appropriate
Really the best option is to fix the underly inefficiency so it actually can return blind block instead of error
ProduceBlindedBlock
ProduceBlindedBlock
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm ok with adding additional defensive checks.
What type of PR is this?
Bug fix
What does this PR do? Why is it needed?
ProduceBlindedBlock
currently assumes that v1alpha1 server will return blinded blocks. This doesn't have to be true. When we get a full block or the builder is not configured, we won't be able to deal with the block so we should return an error.Which issues(s) does this PR fix?
Part of #12103