-
Notifications
You must be signed in to change notification settings - Fork 344
write to the correctly scoped chocolateyErrored variable #658
Conversation
…se chocolatey is intercepted from a module (like boxstarter)
None of this code exists in choco.exe :( |
Right but it fixes the PS version. When is choco.exe due? |
January 15th-ish |
Oh ok. As a full release or alpha/beta? Sent from my Windows Phone From: Rob Reynoldsmailto:notifications@github.com January 15th-ish Reply to this email directly or view it on GitHub: |
Well likely a beta. On Monday, January 12, 2015, Matt Wrock notifications@github.com wrote:
Rob http://devlicio.us/blogs/rob_reynolds |
ok cool. Wasn't sure if there is stuff out there that would be highly impacted by a lack of a non-zero error code. I pushed a work around in boxstarter last night so its not affected. |
I will likely go ahead on this one. |
This looks like a fix for #568 (ha, transposed! Wild!) |
Merged into stable at bcea921 |
Thanks @ferventcoder! |
Released as well a little while ago. |
Exceptions raised in chocolateyInstall.ps1 are not resulting in a non-zero exit code because it is writing to the
$chocolateyErrored
variable in a different scope from where it was created. To illustrate, the added test in this PR will fail ifChocolatey-Nuget.ps1
is reverted.