Network default not loading correct config settings #4402
Assignees
Comments
stringhandler
pushed a commit
that referenced
this issue
Aug 8, 2022
Description --- Uses `network` value from cli, config, then default (currently, Esmeralda) in that order. The network is read from the config file before getting and applying config overrides. Fixes #4402 Motivation and Context --- On the base node, the network would need to be explicitly provided on the cli for config file overrides to be applied. The network value set in the config file was previously ignored. The default network `Network::default()` is set in one place for every application. How Has This Been Tested? --- Manually: - not setting a network in cli on the base node and checking that esme is used - changing network on in the config file and checking that it is used
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you run the base_node as
cargo run --bin tari_base_nodeThe node will run in the default network which is Esmeralda.
But the node will not read the correct config settings from
config.tomlRunning the node as
cargo run --bin tari_base_node -- -- network esmeraldasolves this and the node reads the correct settingThe text was updated successfully, but these errors were encountered: