choco install with `stopOnFirstPackageFailure` enabled results in incorrect package count reported
- Dominant language
- C#
- Stars
- 11.5k
- Forks
- 960
- PR merge metrics
- No merged PRs in 30d
Description
### What You Are Seeing?
When installing a package that fails and `stopOnFirstPackageFailure` is enabled, the results report `0/0 installed packages`
### What is Expected?
It should report the correct number of packages installed.
### How Did You Get This To Happen? (Steps to Reproduce)
**NOTE:** These steps make sure of an internal testing package. It is expected that you have access to this package.
1. `choco feature enable -n stopOnFirstPackageFailure`
2. `choco install badurl`
3. Observe the output indicates `0/0 installed packages`
4. `choco feature disable -n stopOnFirstPackageFailure`
5. `choco install badurl`
6. Observe that the output indicates `0/1 installed packages`
### System Details
* OS Build: `10.0.19043.0
* Windows PowerShell version (Run: `$PSVersionTable`): 5.1
* Chocolatey version (Run `choco --version`): 1.1.0
### Output Log
https://gist.github.com/corbob/b716f1c127468edd241b45211ca96ec3
Contributor guide
Research direction
Start by reproducing the two command sequences in the issue with stopOnFirstPackageFailure enabled and disabled, then compare the reported package counts with the output log. The issue names no source files or tests; done means the failing-install path reports the correct installed-package count and the existing behavior remains correct when the feature is disabled.
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
- Mostly clear
- Newbie friendliness
- 35/100