Skip to content
This repository was archived by the owner on Feb 17, 2025. It is now read-only.

cherry-pick Fix/3200 l1inforoot error on reorg (#3201)#3207

Merged
joanestebanr merged 2 commits into
developfrom
fix/cherry-pick-3200-l1inforoot_error_on_reorg
Feb 6, 2024
Merged

cherry-pick Fix/3200 l1inforoot error on reorg (#3201)#3207
joanestebanr merged 2 commits into
developfrom
fix/cherry-pick-3200-l1inforoot_error_on_reorg

Conversation

@joanestebanr
Copy link
Copy Markdown
Contributor

@joanestebanr joanestebanr commented Feb 5, 2024

  • L1InfooTree cache is calculated when needed and is discard when a reorg happens

Closes #3200
original PR over v0.5.5 : #3201
Commit: 112bdd069179fbee3225c4fae6074ae33b8e249e

What does this PR do?

Reviewers

Main reviewers:

Codeowner reviewers:

  • @-Alice
  • @-Bob

* L1InfooTree cache is calculated when needed and is discard when a reorg happens
@joanestebanr joanestebanr added synchronizer cherry-picked Content has been cherry-picked into a higher version branch zkevm-bridge-sync-rpc labels Feb 5, 2024
@joanestebanr joanestebanr added this to the v0.6.0 milestone Feb 5, 2024
@joanestebanr joanestebanr self-assigned this Feb 5, 2024
@cla-bot cla-bot Bot added the cla-signed label Feb 5, 2024
@joanestebanr joanestebanr merged commit 31959f5 into develop Feb 6, 2024
@joanestebanr joanestebanr deleted the fix/cherry-pick-3200-l1inforoot_error_on_reorg branch February 6, 2024 08:33
@joanestebanr joanestebanr added cherry-pick Content comes from a previous version branch and removed cherry-picked Content has been cherry-picked into a higher version branch labels Feb 6, 2024
@LinkRiver-Vitor
Copy link
Copy Markdown

Hello, guys!

Cross-posting from here

Seems this was the final fix from the issue above. Is there a way to manually force this cache discard?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cherry-pick Content comes from a previous version branch cla-signed synchronizer zkevm-bridge-sync-rpc

Projects

None yet

Development

Successfully merging this pull request may close these issues.

When a L1 reorg happens, the L1InfoTree cache is not updated

3 participants