Skip to content

Fix getSnapshotProposerSequence#1796

Merged
cffls merged 1 commit intov2.3.1-beta-candidatefrom
fix_api_getsnapshot
Sep 29, 2025
Merged

Fix getSnapshotProposerSequence#1796
cffls merged 1 commit intov2.3.1-beta-candidatefrom
fix_api_getsnapshot

Conversation

@cffls
Copy link
Copy Markdown
Contributor

@cffls cffls commented Sep 29, 2025

Description

Use the correct block number for retrieving the snapshot. This is change is required because the behavior of snapshot() in bor consensus had changed. Before, it was expecting the caller to pass the parent block of the target block, but now it is expecting the target block to be directly passed in.

Tested in a devnode.

Changes

  • Bugfix (non-breaking change that solves an issue)
  • Hotfix (change that solves an urgent issue, and requires immediate attention)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (change that is not backwards-compatible and/or changes current functionality)
  • Changes only for a subset of nodes

Use the correct block number for retrieving the snapshot.
This is change is required because the behavior  of `snapshot()` in bor consensus had changed. Before, it was expecting the caller to pass the parent block of the target block, but now it is expecting the target block to be directly passed in.
@sonarqubecloud
Copy link
Copy Markdown

Copy link
Copy Markdown
Contributor

@lucca30 lucca30 left a comment

Choose a reason for hiding this comment

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

lgtm

@cffls cffls merged commit 7cdc467 into v2.3.1-beta-candidate Sep 29, 2025
7 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.

2 participants