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

Cannot set verbosity to info in the command-line tool when the env var is set to something else #666

Closed
adamralph opened this issue Feb 1, 2022 · 2 comments · Fixed by #667
Labels
bug Something isn't working
Milestone

Comments

@adamralph
Copy link
Owner

Version(s)

  • 2.4.0
  • 2.5.0

To reproduce

Steps to reproduce the behaviour:

  1. Set the MinVerVerbosity env var to anything other than info
  2. Run minver with --verbosity info

Expected behaviour

minver runs with info level verbosity.

Actual behaviour

minver runs with the verbosity level set by the env var.

Workarounds

Unset the MinVerVerbosity instead of overriding it with --verbosity info.

Additional context

n/a

@adamralph adamralph added the bug Something isn't working label Feb 1, 2022
@adamralph adamralph added this to the 3.0.0 milestone Feb 1, 2022
@adamralph adamralph linked a pull request Feb 1, 2022 that will close this issue
@adamralph adamralph removed a link to a pull request Feb 1, 2022
@adamralph adamralph linked a pull request Feb 1, 2022 that will close this issue
@adamralph
Copy link
Owner Author

fixed in #667

@adamralph
Copy link
Owner Author

released in 3.0.0-rc.2

@adamralph adamralph changed the title Cannot set verbosity to info in the CLI tool when the env var is set to something else Cannot set verbosity to info in the command-line tool when the env var is set to something else Mar 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant