Skip to content
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

Upstream v2.60.1 #184

Merged
merged 27 commits into from
Jun 7, 2024
Merged

Upstream v2.60.1 #184

merged 27 commits into from
Jun 7, 2024

Conversation

mininny
Copy link
Member

@mininny mininny commented Jun 4, 2024

taratorio and others added 25 commits May 17, 2024 23:43
…0396)

Cherry-pick:
erigontech@bc5fa6f

Need this to get PR CI green for v2.60.1 patches, e.g. -
erigontech#10390

Co-authored-by: Andrew Ashikhmin <[email protected]>
Cherry pick PR erigontech#10451 into the release branch

Co-authored-by: mars <[email protected]>
Cherry pick PR erigontech#10281 into the release branch

Co-authored-by: Mark Holt <[email protected]>
Co-authored-by: alex.sharov <[email protected]>
Cherry pick PR erigontech#10460 into the release branch

Co-authored-by: Willian Mitsuda <[email protected]>
Otherwise: if start after `kill -9` in the middle of merge - may remove
small files of 1 type of file, but leave small files of another type of
files (which merge was not finished) - and leave node in un-mergable
state: erigontech#10485

---------

Co-authored-by: awskii <[email protected]>
Cherry pick PR erigontech#10468 into the release branch

Co-authored-by: Mark Holt <[email protected]>
Cherry pick PR erigontech#10493 into the release branch

Co-authored-by: Mark Holt <[email protected]>
Fixes a recent regression causing unwinds due to checkpoints having zero
root hash:
```
[WARN] [05-18|23:58:54.662] [bor] Root hash mismatch while whitelisting checkpoint expected=ac1c57270479250af3ce8eee90075cd8b2ba1bac55353105e063d9a4c87c743e got=0000000000000000000000000000000000000000000000000000000000000000
[WARN] [05-18|23:58:54.662] [bor] Rewinding chain due to checkpoint root hash mismatch number=57125727
```

Note this has already been fixed on Erigon 3 branch but as part of a
non-related PR -
https://github.com/ledgerwatch/erigon/pull/10124/files#diff-47d4532f399f2d6a45e6f19944a45c80bac573b4d1b5cb51485d0254229d1b16
Cherry pick PR erigontech#10528 into the release branch

Co-authored-by: Shoham Chakraborty <[email protected]>
Cherry pick PR erigontech#10546 into the release branch

Co-authored-by: Giulio rebuffo <[email protected]>
…racters (erigontech#10578)

Cherry pick PR erigontech#10512 into the release branch

Co-authored-by: Giulio rebuffo <[email protected]>
Problem: `+1` was added to maxBlockNum instead of minBlockNum
for: erigontech#10554
Comment on lines +157 to +167
chainConfig, err := api.chainConfig(ctx, dbtx)
if err != nil {
return 0, fmt.Errorf("read chain config: %v", err)
}

// Handle pre-bedrock blocks
blockNum, err := api.blockNumberFromBlockNumberOrHash(dbtx, &bNrOrHash)
latestCanBlockNumber, latestCanHash, isLatest, err := rpchelper.GetCanonicalBlockNumber(latestNumOrHash, dbtx, api.filters) // DoCall cannot be executed on non-canonical blocks
if err != nil {
return 0, err
}
chainConfig, err := api.chainConfig(ctx, dbtx)
if err != nil {
return 0, fmt.Errorf("read chain config: %v", err)
}
if chainConfig.IsOptimismPreBedrock(blockNum) {

if chainConfig.IsOptimismPreBedrock(latestCanBlockNumber) {
Copy link
Member Author

Choose a reason for hiding this comment

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

Upstream change of getting the block number from dbtx

@ImTei
Copy link
Member

ImTei commented Jun 5, 2024

@mininny 👍 please resolve the CI failure

@mininny
Copy link
Member Author

mininny commented Jun 5, 2024

@mininny 👍 please resolve the CI failure

The tests are fixed! :) bb12285

@mininny
Copy link
Member Author

mininny commented Jun 6, 2024

Added the op-erigon version bump up to 0.6.1: ebeb01d

@mininny mininny merged commit a63007d into op-erigon Jun 7, 2024
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants