-
Notifications
You must be signed in to change notification settings - Fork 267
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
Conflicting --validators-keystore-locking-enabled=false
has Teku complain about --ee-endpoint
#6146
Comments
--validators-keystore-locking-enabled=false
has Teku complain about --ee-endpoint
--validators-keystore-locking-enabled=false
has Teku complain about --ee-endpoint
hmm, that definitely is unexpected. It doesn't happen with a simpler command line (eg I think something is going wrong because both We'll need to dig further to work out exactly why we're getting such an odd error because of that - the last version of the option should just take precedence. |
Simplest version I can find that reproduces this is:
|
I think it's somehow related to the fact that |
I tried approaching it by adding another pass which sorts the provided params by matched group, but it's not that straight forward... |
Basically we need to stop using arggroups, and still get help text out in a nice format. |
Description
When adding
--validators-keystore-locking-enabled=false
to Teku startup parameters, while mistakenly not removing--validators-keystore-locking-enabled=true
, it complains thatFATAL - Invalid configuration. --ee-endpoint parameter is mandatory when Bellatrix milestone is enabled
Which is unexpected to say the least. A more fitting error message about conflicting parameters would be helpful.
Command line as shown by
ps -aux | grep teku
:Versions (Add all that apply)
teku/v22.8.2/linux-x86_64/-eclipseadoptium-openjdk64bitservervm-java-17
The text was updated successfully, but these errors were encountered: