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

Node can no longer synchronize with latest versions of op-node and op-reth #12482

Closed
1 task done
MrFrogoz opened this issue Nov 12, 2024 · 4 comments · Fixed by #12520
Closed
1 task done

Node can no longer synchronize with latest versions of op-node and op-reth #12482

MrFrogoz opened this issue Nov 12, 2024 · 4 comments · Fixed by #12520
Labels
C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled

Comments

@MrFrogoz
Copy link

Describe the bug

ethereum-optimism/optimism#12897

Steps to reproduce

ethereum-optimism/optimism#12897

Node logs


Platform(s)

Linux (x86)

What version/commit are you on?

reth-optimism-cli Version: 1.1.1
Commit SHA: 15c230b
Build Timestamp: 2024-11-05T12:40:14.182399522Z
Build Features: asm_keccak,jemalloc,optimism
Build Profile: maxperf

What database version are you on?

latest

Which chain / network are you on?

optimism and base

What type of node are you running?

Archive (default)

What prune config do you use, if any?

No response

If you've built Reth from source, provide the full command you used

No response

Code of Conduct

  • I agree to follow the Code of Conduct
@MrFrogoz MrFrogoz added C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled labels Nov 12, 2024
@mattsse
Copy link
Collaborator

mattsse commented Nov 12, 2024

hmm, this seems similar to #12470

@mattsse
Copy link
Collaborator

mattsse commented Nov 13, 2024

thanks for flagging,
somehow we never Hit this on our infra...
sorry about this, expediting new release with fix #12520 in the meantime please use 1.1.0

@MrFrogoz
Copy link
Author

MrFrogoz commented Nov 13, 2024

Thanks, for now I have moved all the clusters to 1.0.8 because 1.1.0 crashes due to a bug that you already fixed

@mattsse
Copy link
Collaborator

mattsse commented Nov 13, 2024

really, sorry about this
expect 1.1.2 monday

@github-project-automation github-project-automation bot moved this from Todo to Done in Reth Tracker Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants