-
Notifications
You must be signed in to change notification settings - Fork 998
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
release v1.1.1 #2641
Merged
release v1.1.1 #2641
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add "P2P Networking" to "Merge" section
Co-authored-by: Hsiao-Wei Wang <hsiaowei.eth@gmail.com>
Expand If_and_only_if in `execute_payload`
Some tests are currently restricted to a single phase using @with_phases even though they could likely run unchanged in later phases. This patch changes the default for such tests to also run in later phases. If the beacon chain changes enough in later phases to break these tests, this highlights that the tests need to be adjusted or extended accordingly.
Fix `initialize_beacon_state_from_eth1` previous_version
There are two similar functions to compute the timestamp for a given beacon chain slot. `compute_time_at_slot` is used for processing Eth1 votes, and does not take into account `GENESIS_TIME`. The other one, `compute_timestamp_at_slot`, is used everywhere else. When processing `ExecutionPayload`, the `merge/beacon-chain.md` spec uses the latter, `compute_timestamp_at_slot`, to verify the timestamp. However, in the test code, `build_empty_execution_payload` uses `compute_time_at_slot`. This patch changes the test to use the same function for creating the timestamp that is later used to verify it. Note that `GENESIS_TIME` is 0 so there is no practical difference.
run tests against future forks by default
use correct timestamp for empty ExecutionPayload
initialize_beacon_state_from_eth1 for pre-transition merge
bump version.txt to v1.1.1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release some minor fixes to merge spec for interop testing
Altair stable, other than fixed
initialize_beacon_state_from_eth1
(not currently used in production)todo: