-
Notifications
You must be signed in to change notification settings - Fork 747
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
Update to consensus spec v1.4.0-beta.6 #5094
Update to consensus spec v1.4.0-beta.6 #5094
Conversation
Looks like a couple unit tests are broken |
the new fork choice change introduces |
I just pushed 1a06c72 which fixes the |
I reverted 0c875b0 and added 1beddec. I believe the latter is the appropriate fix since it precisely modifies the existing tests to be compatible with the new FC changes. The fork choice definition tests that I've changed are very basic tests. I highly doubt they're of any value to consensus-specs, however I'm not certain enough that they're fully overlapping to delete these tests from our codebase. |
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.
Thanks for the help @paulhauner, love the new comments on the tests.
@dapplion are you able to check this one out again? |
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.
Looks good! Appreciate the thorough comments
@Mergifyio queue |
🛑 The pull request has been removed from the queue
|
@Mergifyio requeue |
❌ This pull request head commit has not been previously disembarked from queue. |
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 4172d9f |
* get latest ef tests passing * fix tests * Fix invalid payload recovery tests * Merge branch 'unstable' into update-to-spec-v1.4.0-beta.6 * Revert "fix tests" This reverts commit 0c875b0. * Fix fork choice def. tests * Update beacon_node/beacon_chain/tests/payload_invalidation.rs
Issue Addressed
Resolves #5083
Proposed Changes
fake_crypto
feature gate forkzg_inclusion_merkle_proof_validity
- tests here were added that include (mostly) randomly constructed beacon block bodies, they wouldn't deserialize without stubbing out BLST Add randomized block
blob_kzg_commitment_merkle_proof
cases ethereum/consensus-specs#3555Additional Info
cached_head.finalized_checkpoint()
everywhere here, which is the correct checkpoint, so there were no updates required for this Use fork choice to determinefinalized_checkpoint
in gossip validation ethereum/consensus-specs#3543