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

Clean up conflicting base node configs #4909

Closed
sdbondi opened this issue Nov 11, 2022 · 0 comments
Closed

Clean up conflicting base node configs #4909

sdbondi opened this issue Nov 11, 2022 · 0 comments
Assignees
Labels
A-base_node Area - The Tari base node executable and libraries C-bug Category - fixes a bug, typically associated with an issue.

Comments

@sdbondi
Copy link
Member

sdbondi commented Nov 11, 2022

There are a few duplicate config keys that exist in the base node config and the base node state machine config
meaning settings and behaviour could mismatch.

base_node.max_randomx_vms (this setting will not work)
base_node.bypass_range_proof_verification (this setting will not work)
base_node.force_sync_peers (this was fixed in #4647 but the fix is a bit hacky)

pub struct BaseNodeStateMachineConfig {

https://github.com/tari-project/tari/blob/development/applications/tari_base_node/src/config.rs#L109

ref #4646

@sdbondi sdbondi added C-bug Category - fixes a bug, typically associated with an issue. A-base_node Area - The Tari base node executable and libraries labels Nov 11, 2022
@sdbondi sdbondi added this to the Stagenet Freeze milestone Nov 11, 2022
@sdbondi sdbondi moved this to Bugs in Tari Esme Testnet Nov 11, 2022
@sdbondi sdbondi moved this from Bugs to In Progress in Tari Esme Testnet Nov 14, 2022
@sdbondi sdbondi moved this from In Progress to In Review in Tari Esme Testnet Nov 22, 2022
stringhandler pushed a commit that referenced this issue Nov 23, 2022
Description
---
Removed `max_randomx_vms` from `BaseNodeStateMachineConfig` and the config preset, now passing the initialized RandomXFactory in via the initializer, same for `bypass_range_proof_verification` but passing only the setting


Motivation and Context
---
#4909

There are a few duplicate config keys that exist in the base node config and the base node state machine config
meaning settings and behaviour could mismatch.

`base_node.max_randomx_vms` (this setting will not work)
`base_node.bypass_range_proof_verification` (this setting will not work)
`base_node.force_sync_peers` (this was fixed in #4647 but the fix is a bit hacky) 

https://github.com/tari-project/tari/blob/956b27954dda1f15f82bff0ba0ba0ee1f0880d2d/base_layer/core/src/base_node/state_machine_service/state_machine.rs#L52

https://github.com/tari-project/tari/blob/development/applications/tari_base_node/src/config.rs#L109

ref #4646

How Has This Been Tested?
---
manually
@stringhandler stringhandler moved this from In Review to Done in Tari Esme Testnet Nov 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-base_node Area - The Tari base node executable and libraries C-bug Category - fixes a bug, typically associated with an issue.
Projects
Archived in project
Development

No branches or pull requests

3 participants