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

core/state: no need to prune block if the same #1332

Merged
merged 3 commits into from
Jan 22, 2024

Conversation

jsvisa
Copy link
Contributor

@jsvisa jsvisa commented Mar 2, 2023

Description

Don't need to run prune-block if specified reserve blocks are the same to items in ancientdb

@jsvisa jsvisa changed the base branch from master to develop March 2, 2023 02:12
@jsvisa jsvisa force-pushed the bugfix/prune-block-ancient-dir branch from 0fefa12 to 282e7db Compare March 2, 2023 10:56
@jsvisa
Copy link
Contributor Author

jsvisa commented Apr 21, 2023

@brilliant-lx and please take a look at this one

brilliant-lx
brilliant-lx previously approved these changes May 6, 2023
@brilliant-lx
Copy link
Collaborator

brilliant-lx commented May 6, 2023

@brilliant-lx and please take a look at this one

got it, thx
but the UT failed, could you check the UT, or you may rebase you branch to latest develop

@jsvisa jsvisa force-pushed the bugfix/prune-block-ancient-dir branch 2 times, most recently from eafdf1c to aaa29e7 Compare May 23, 2023 06:47
joeylichang
joeylichang previously approved these changes Jan 9, 2024
@jsvisa jsvisa dismissed joeylichang’s stale review January 9, 2024 09:17

The merge-base changed after approval.

@joeylichang
Copy link
Contributor

LGTM, it checks the --block-amount-reserved params that from prune block cmd flag and BlockAmountReserved(ancient dir date items) equal.

RenRick
RenRick previously approved these changes Jan 9, 2024
Copy link

@RenRick RenRick left a comment

Choose a reason for hiding this comment

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

LGTM

@jsvisa jsvisa dismissed RenRick’s stale review January 9, 2024 09:22

The merge-base changed after approval.

@zzzckck
Copy link
Collaborator

zzzckck commented Jan 9, 2024

@jsvisa could you rebase your branch to latest develop?

@zzzckck
Copy link
Collaborator

zzzckck commented Jan 22, 2024

@jsvisa could you rebase your branch? or we may create a separate PR to include your change.

Signed-off-by: Delweng <delweng@gmail.com>
This reverts commit 1bbd4b8.

Signed-off-by: Delweng <delweng@gmail.com>
Signed-off-by: Delweng <delweng@gmail.com>
@jsvisa jsvisa force-pushed the bugfix/prune-block-ancient-dir branch from aaa29e7 to d0539a4 Compare January 22, 2024 08:22
@jsvisa
Copy link
Contributor Author

jsvisa commented Jan 22, 2024

@zzzckck sorry for the late reply, finished rebasing.

@zzzckck zzzckck changed the title Bugfix/prune block ancient dir core/state: no need to prune block if the same Jan 22, 2024
@zzzckck zzzckck merged commit a6a9562 into bnb-chain:develop Jan 22, 2024
6 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.

5 participants