Skip to content

[Merged by Bors] - v3.0.0#3464

Closed
paulhauner wants to merge 2 commits intounstablefrom
cut-v3.0.0
Closed

[Merged by Bors] - v3.0.0#3464
paulhauner wants to merge 2 commits intounstablefrom
cut-v3.0.0

Conversation

@paulhauner
Copy link
Copy Markdown
Member

@paulhauner paulhauner commented Aug 12, 2022

@paulhauner paulhauner added work-in-progress PR is a work-in-progress do-not-merge v3.0.0 🐼 Required for the v3.0.0 release labels Aug 12, 2022
@paulhauner
Copy link
Copy Markdown
Member Author

paulhauner commented Aug 16, 2022

I'm going to try adding these tests now: https://github.com/ethereum/consensus-specs/releases/tag/v1.2.0-rc.2 Actually, I'll do that here: #3462 (comment)

@paulhauner
Copy link
Copy Markdown
Member Author

I've just rebased this onto unstable.

@paulhauner
Copy link
Copy Markdown
Member Author

Once again, rebased on unstable ☺️

@paulhauner
Copy link
Copy Markdown
Member Author

For those watching, the plan is to test this PR over the weekend and then publish a release Monday (AEST).

@paulhauner
Copy link
Copy Markdown
Member Author

We have had this running over the weekend on Prater and Mainnet on several nodes. I am happy with the amount of testing and I think we're good to review and merge 🎉

@paulhauner paulhauner added ready-for-review The code is ready for review and removed work-in-progress PR is a work-in-progress do-not-merge labels Aug 21, 2022
@michaelsproul michaelsproul marked this pull request as ready for review August 21, 2022 23:19
Copy link
Copy Markdown
Member

@michaelsproul michaelsproul left a comment

Choose a reason for hiding this comment

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

Magnifique! 🎉

I'm excited! 🚀

@paulhauner
Copy link
Copy Markdown
Member Author

🚀 🐼 🚀

bors r+

bors bot pushed a commit that referenced this pull request Aug 21, 2022
## Issue Addressed

NA

## Proposed Changes

Bump versions to v3.0.0

## Additional Info

- ~~Blocked on #3439~~
- ~~Blocked on #3459~~
- ~~Blocked on #3463~~
- ~~Blocked on #3462~~
- ~~Requires further testing~~
@Sonixier
Copy link
Copy Markdown

Let's go!

@bors
Copy link
Copy Markdown

bors bot commented Aug 22, 2022

Build failed:

@michaelsproul
Copy link
Copy Markdown
Member

spurious CI failure

bors retry

bors bot pushed a commit that referenced this pull request Aug 22, 2022
## Issue Addressed

NA

## Proposed Changes

Bump versions to v3.0.0

## Additional Info

- ~~Blocked on #3439~~
- ~~Blocked on #3459~~
- ~~Blocked on #3463~~
- ~~Blocked on #3462~~
- ~~Requires further testing~~
@bors
Copy link
Copy Markdown

bors bot commented Aug 22, 2022

Build failed:

@michaelsproul
Copy link
Copy Markdown
Member

bors retry

bors bot pushed a commit that referenced this pull request Aug 22, 2022
## Issue Addressed

NA

## Proposed Changes

Bump versions to v3.0.0

## Additional Info

- ~~Blocked on #3439~~
- ~~Blocked on #3459~~
- ~~Blocked on #3463~~
- ~~Blocked on #3462~~
- ~~Requires further testing~~
@michaelsproul michaelsproul added ready-for-merge This PR is ready to merge. and removed ready-for-review The code is ready for review labels Aug 22, 2022
@bors
Copy link
Copy Markdown

bors bot commented Aug 22, 2022

Build failed:

@paulhauner
Copy link
Copy Markdown
Member Author

Fix for cargo-udeps authored by @michaelsproul has been added in: 6ce9dc7

@paulhauner
Copy link
Copy Markdown
Member Author

Lets just try bors again.

bors r+

bors bot pushed a commit that referenced this pull request Aug 22, 2022
## Issue Addressed

NA

## Proposed Changes

Bump versions to v3.0.0

## Additional Info

- ~~Blocked on #3439~~
- ~~Blocked on #3459~~
- ~~Blocked on #3463~~
- ~~Blocked on #3462~~
- ~~Requires further testing~~


Co-authored-by: Michael Sproul <michael@sigmaprime.io>
@bors
Copy link
Copy Markdown

bors bot commented Aug 22, 2022

Build failed:

@paulhauner
Copy link
Copy Markdown
Member Author

bors r+

bors bot pushed a commit that referenced this pull request Aug 22, 2022
## Issue Addressed

NA

## Proposed Changes

Bump versions to v3.0.0

## Additional Info

- ~~Blocked on #3439~~
- ~~Blocked on #3459~~
- ~~Blocked on #3463~~
- ~~Blocked on #3462~~
- ~~Requires further testing~~


Co-authored-by: Michael Sproul <michael@sigmaprime.io>
@bors bors bot changed the title v3.0.0 [Merged by Bors] - v3.0.0 Aug 22, 2022
@bors bors bot closed this Aug 22, 2022
@michaelsproul michaelsproul deleted the cut-v3.0.0 branch August 22, 2022 06:25
bors bot pushed a commit that referenced this pull request Aug 24, 2022
## Issue Addressed

Resolves #3448

## Proposed Changes

Removes a known failure that wasn't actually a known failure. The tests declare this block invalid and we refuse to import it due to `ExecutionPayloadError(UnverifiedNonOptimisticCandidate)`.

This is correct since there is only one "eth1" block included in this test and two are required to trigger the merge (pre- and post-TTD blocks). It is slot 1 (tick = 12s) when this block is imported so the import must be prevented by `SAFE_SLOTS_TO_IMPORT_OPTIMISTICALLY`.

I'm not sure where I got the idea in #3448 that this test needed retrospective checking, that seems like a false assumption in hindsight.

## Additional Info

- Blocked on #3464
bors bot pushed a commit that referenced this pull request Aug 24, 2022
## Issue Addressed

NA

## Proposed Changes

Indicate that local keystores are `readonly: Some(false)` rather than `None` via the `/eth/v1/keystores` method on the VC API.

I'll mark this as backwards-incompat so we remember to mention it in the release notes. There aren't any type-level incompatibilities here, just a change in how Lighthouse responds to responses.

## Additional Info

- Blocked on #3464
Woodpile37 pushed a commit to Woodpile37/lighthouse that referenced this pull request Jan 6, 2024
## Issue Addressed

NA

## Proposed Changes

Bump versions to v3.0.0

## Additional Info

- ~~Blocked on sigp#3439~~
- ~~Blocked on sigp#3459~~
- ~~Blocked on sigp#3463~~
- ~~Blocked on sigp#3462~~
- ~~Requires further testing~~


Co-authored-by: Michael Sproul <michael@sigmaprime.io>
Woodpile37 pushed a commit to Woodpile37/lighthouse that referenced this pull request Jan 6, 2024
## Issue Addressed

Resolves sigp#3448

## Proposed Changes

Removes a known failure that wasn't actually a known failure. The tests declare this block invalid and we refuse to import it due to `ExecutionPayloadError(UnverifiedNonOptimisticCandidate)`.

This is correct since there is only one "eth1" block included in this test and two are required to trigger the merge (pre- and post-TTD blocks). It is slot 1 (tick = 12s) when this block is imported so the import must be prevented by `SAFE_SLOTS_TO_IMPORT_OPTIMISTICALLY`.

I'm not sure where I got the idea in sigp#3448 that this test needed retrospective checking, that seems like a false assumption in hindsight.

## Additional Info

- Blocked on sigp#3464
Woodpile37 pushed a commit to Woodpile37/lighthouse that referenced this pull request Jan 6, 2024
## Issue Addressed

NA

## Proposed Changes

Indicate that local keystores are `readonly: Some(false)` rather than `None` via the `/eth/v1/keystores` method on the VC API.

I'll mark this as backwards-incompat so we remember to mention it in the release notes. There aren't any type-level incompatibilities here, just a change in how Lighthouse responds to responses.

## Additional Info

- Blocked on sigp#3464
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-merge This PR is ready to merge. v3.0.0 🐼 Required for the v3.0.0 release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants