NuGet errors are reported to stdout instead of stderr
Open
0 - Backlog
Blocked - External
Bug
Dependency - Chocolatey.NuGet.Client
- Dominant language
- C#
- Stars
- 11.5k
- Forks
- 960
- PR merge metrics
- No merged PRs in 30d
Description
### What You Are Seeing?
Any errors encountered during "choco outdated" are reported to stdout instead of stderr
### What is Expected?
Errors should be reported on stderr
### How Did You Get This To Happen? (Steps to Reproduce)
choco outdated --limit-output --nocolor --ignore-pinned --no-progress --fail-on-stderr -s https://127.0.0.1/doesnt/exist --ignore-unfound 2>NUL
### Output Log
[NuGet] An error occurred while loading packages from 'https://127.0.0.1/doesnt/exist': Unable to connect to the remote server
[NuGet] An error occurred while loading packages from 'https://127.0.0.1/doesnt/exist': Unable to connect to the remote server
[NuGet] An error occurred while loading packages from 'https://127.0.0.1/doesnt/exist': Unable to connect to the remote server
Contributor guide
Research direction
Start by reproducing the reported choco outdated command and trace how errors from the NuGet source are emitted. Done means those errors go to stderr, leaving stdout free of the error messages when stderr is redirected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100