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: fix Execution stage unwind after invalid block #2360

Merged
merged 2 commits into from
Sep 18, 2024

Conversation

canepat
Copy link
Member

@canepat canepat commented Sep 17, 2024

Fixes #2359

This PR restores in stage Execution the invalid block handling logic removed in #1511

Also fixes the invalid block reference lifetime issue causing an incorrect block hash to be stored as bad block hash in SyncContext and displayed into the warning log, as described in #2358

@canepat canepat added the maintenance Some maintenance work (fix, refactor, rename, test...) label Sep 17, 2024
@canepat canepat marked this pull request as ready for review September 17, 2024 19:42
@battlmonstr battlmonstr merged commit c0d6ded into master Sep 18, 2024
6 checks passed
@battlmonstr battlmonstr deleted the node_fix_stage_execution_invalid_block branch September 18, 2024 08:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Some maintenance work (fix, refactor, rename, test...)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

silkworm: inconsistent database content after unwind
2 participants