-
Notifications
You must be signed in to change notification settings - Fork 788
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
Non-release profiles of lcli
panic by default due to argument processing failure
#4488
Labels
bug
Something isn't working
low-hanging-fruit
Easy to resolve, get it before someone else does!
v4.4.1
ETA August 2023
Comments
jmcph4
added
bug
Something isn't working
v4.4.1
ETA August 2023
low-hanging-fruit
Easy to resolve, get it before someone else does!
labels
Jul 11, 2023
bors bot
pushed a commit
that referenced
this issue
Jul 11, 2023
## Issue Addressed #4488 ## Proposed Changes - Remove all instances of the `required` modifier where we have a default value specified for a subcommand ## Additional Info N/A
bors bot
pushed a commit
that referenced
this issue
Jul 12, 2023
## Issue Addressed #4488 ## Proposed Changes - Remove all instances of the `required` modifier where we have a default value specified for a subcommand ## Additional Info N/A
bors bot
pushed a commit
that referenced
this issue
Jul 12, 2023
## Issue Addressed #4488 ## Proposed Changes - Remove all instances of the `required` modifier where we have a default value specified for a subcommand ## Additional Info N/A
bors bot
pushed a commit
that referenced
this issue
Jul 12, 2023
## Issue Addressed #4488 ## Proposed Changes - Remove all instances of the `required` modifier where we have a default value specified for a subcommand ## Additional Info N/A
bors bot
pushed a commit
that referenced
this issue
Jul 12, 2023
## Issue Addressed #4488 ## Proposed Changes - Remove all instances of the `required` modifier where we have a default value specified for a subcommand ## Additional Info N/A
bors bot
pushed a commit
that referenced
this issue
Jul 13, 2023
## Issue Addressed #4488 ## Proposed Changes - Remove all instances of the `required` modifier where we have a default value specified for a subcommand ## Additional Info N/A
bors bot
pushed a commit
that referenced
this issue
Jul 13, 2023
## Issue Addressed #4488 ## Proposed Changes - Remove all instances of the `required` modifier where we have a default value specified for a subcommand ## Additional Info N/A
bors bot
pushed a commit
that referenced
this issue
Jul 13, 2023
## Issue Addressed #4488 ## Proposed Changes - Remove all instances of the `required` modifier where we have a default value specified for a subcommand ## Additional Info N/A
bors bot
pushed a commit
that referenced
this issue
Jul 13, 2023
## Issue Addressed #4488 ## Proposed Changes - Remove all instances of the `required` modifier where we have a default value specified for a subcommand ## Additional Info N/A
bors bot
pushed a commit
that referenced
this issue
Jul 13, 2023
## Issue Addressed #4488 ## Proposed Changes - Remove all instances of the `required` modifier where we have a default value specified for a subcommand ## Additional Info N/A
bors bot
pushed a commit
that referenced
this issue
Jul 14, 2023
## Issue Addressed #4488 ## Proposed Changes - Remove all instances of the `required` modifier where we have a default value specified for a subcommand ## Additional Info N/A
bors bot
pushed a commit
that referenced
this issue
Jul 17, 2023
## Issue Addressed #4488 ## Proposed Changes - Remove all instances of the `required` modifier where we have a default value specified for a subcommand ## Additional Info N/A
Woodpile37
pushed a commit
to Woodpile37/lighthouse
that referenced
this issue
Jan 6, 2024
## Issue Addressed sigp#4488 ## Proposed Changes - Remove all instances of the `required` modifier where we have a default value specified for a subcommand ## Additional Info N/A
Woodpile37
pushed a commit
to Woodpile37/lighthouse
that referenced
this issue
Jan 6, 2024
## Issue Addressed sigp#4488 ## Proposed Changes - Remove all instances of the `required` modifier where we have a default value specified for a subcommand ## Additional Info N/A
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
low-hanging-fruit
Easy to resolve, get it before someone else does!
v4.4.1
ETA August 2023
Description
When invoked in non-release profiles,
lcli
panics by default during argument parsing. This is most likely due to an error in Clap: clap-rs/clap#1546.Credit to @jimmygchen for the discovery.
Version
Present Behaviour
Expected Behaviour
Lighthouse should not panic on this condition, but instead display the default help text and return a
1
exit code. Compare the above behaviour to the release profile behaviour:Steps to resolve
As per this comment on the Clap ticket, removing all instances of both
required
anddefault_value
should work:The text was updated successfully, but these errors were encountered: