Copilot crashes on launch if log level is set to any value other than "all" or "default"
Open
Beginner friendly
Nobody has claimed this yet.
area:configuration
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
Describe the bug
Copilot crashes on launch if I try start it with a log level set to any of: none, error, warning, info, debug
Affected version
No response
Steps to reproduce the behavior
copilot --log-level error
Expected behavior
Copilot does not crash when setting a different log level.
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CLI entry point and the argument handling for the --log-level option; the issue does not name a source file or test. Reproduce with copilot --log-level error, then check the other listed levels. Done means none, error, warning, info, and debug no longer crash on launch, while all and default continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100