Skip to content

Using lowercase loglevel argument like in the documentation throws error #6395

@alimony

Description

@alimony

Checklist

  • I have checked the issues list
    for similar or identical bug reports.
  • I have checked the pull requests list
    for existing proposed fixes.
  • I have checked the commit log
    to find out if the bug was already fixed in the master branch.
  • I have included all related issues and possible duplicate issues in this issue
    (If there are none, check this box anyway).

Related Issues and Possible Duplicates

Related Issues

  • None

Possible Duplicates

  • None

Description

When starting workers like some examples in the documentation that uses lowercase info as argument to loglevel I get this error: Error: Invalid value for '-l' / '--loglevel': invalid choice: info. (choose from DEBUG, INFO, WARNING, ERROR, CRITICAL, FATAL). I assume this is because of the change to Click in 5.0.

Suggestions

Review documentation for instances of lowercase loglevel being passed and update them to use uppercase.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions