Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Use target state to compute committees #4235
base: unstable
Are you sure you want to change the base?
Use target state to compute committees #4235
Changes from 4 commits
8c1e17a
9a7bcd6
9acf4d2
9cbc54b
4b22fd9
fd77822
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 concerned we have a race condition here that could make this error reachable, resulting in an ugly
error!
here. The race is:Alternatively:
get_state
and fail, because the state has been pruned. Or (today) load a freezer state at great expense ( 😱 ).This second race is related to #4610.
My preference would be to soak #4160 in Hydra and ensure it's solid before making any changes here. Then we can add this change in maybe with the following defensive changes:
RequestedColdShuffling
error which complicates error handling (reuseAttestationStateIsFinalized
which already has its own handling).get_inconsistent_state_for_attestation_verification_only
in both branches and let it do the check atomically (this change exists on the [Merged by Bors] - Remove the unusedExecutionOptimisticForkVersionedResponse
type #4160 branch).