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

cli: inconsistent and incorrect error placement on flag not defined #6857

Closed
jrasell opened this issue Dec 13, 2019 · 2 comments · Fixed by #6865
Closed

cli: inconsistent and incorrect error placement on flag not defined #6857

jrasell opened this issue Dec 13, 2019 · 2 comments · Fixed by #6865

Comments

@jrasell
Copy link
Member

jrasell commented Dec 13, 2019

Nomad version

Nomad v0.10.2

Operating system and Environment details

Tested on macOS Catalina 10.15.1

Issue

When passing a flag to a Nomad CLI command, which is not defined for use, the output error is inconsistency placed and is also concatenated onto the command usage output. The error will sometimes appear before the command usage, and sometimes after. Both examples are shown below.

Example 1:

$ nomad server members -verbose
flag provided but not defined: -verboseUsage: nomad server members [options]

Example 2 (output shortened):

$ nomad node status -detailed
...
...
  -t
    Format and display node using a Go template.flag provided but not defined: -detailed

Reproduction steps

A couple of commands using incorrect flags:
nomad node status -detailed
nomad server members -verbose

@tgross
Copy link
Member

tgross commented Dec 13, 2019

Hi @jrasell! I've marked this as a bug. Thanks!

@tgross tgross added this to the unscheduled milestone Dec 13, 2019
@notnoop notnoop modified the milestones: unscheduled , 0.10.3 Dec 16, 2019
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants