-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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
Fix no-op pruner setting #17928
Fix no-op pruner setting #17928
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@halfprice is attempting to deploy a commit to the Mysten Labs Team on Vercel. A member of the Team first needs to authorize it. |
e38ee96
to
1428ac5
Compare
crates/sui-node/src/lib.rs
Outdated
@@ -587,13 +587,16 @@ impl SuiNode { | |||
state_snapshot_handle.is_some(), | |||
)?; | |||
|
|||
let mut pruning_config = config.authority_store_pruning_config; | |||
// `genesis` is immutably borrowed from config. So we have to clone a copy here. | |||
let mut config = config.clone(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is so clever i thought it re-introduces the bug.
You could just clone genesis above, which might be less confusing? up to you
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I was debating. I cloned genesis above, and hope that no one clone the genesis from config agian and modify it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
modifying genesis is very unlikely (unless we are trying to inject a failure or something) so this seems better
## Description Describe the changes or additions included in this PR. ## Test plan How did you test the new or updated feature? --- ## Release notes Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required. For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates. - [ ] Protocol: - [ ] Nodes (Validators and Full nodes): - [ ] Indexer: - [ ] JSON-RPC: - [ ] GraphQL: - [ ] CLI: - [ ] Rust SDK:
Description
Describe the changes or additions included in this PR.
Test plan
How did you test the new or updated feature?
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.