fix: correct value for validator_node_timeout consensus constant in localnet #4879
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Changed the
validator_node_timeout
consensus constant from0
to100
in thelocalnet
network.Motivation and Context
We use the
localnet
network in thetari-dan
projectcucumber-rs
integration tests. The current value for thevalidator_node_timeout
constant in that network is0
, which makes the validator node registrations to never be valid. It should be a reasonable value, similar to theigor
network.How Has This Been Tested?
With this change, in the
tari-dan
projectcucumber-rs
integration tests does now list registered validator nodes