Choco: PowerShell - Start-ChocolateyProcessAsAdmin should log to stdout and not stderr

[ferventcoder]

When running with powershell.exe as an external process, it adds all output messages as stderr to the CLIXML stream when those logging streams are not info or output. This behavior seems incorrect.

Related to #901

Details

If you see Exited with '0', it means it is good - those are not actually errors. Bear with me a second - so when you call Start-ChocolateyProcessAsAdmin, it calls that process which runs in a separate PowerShell process to perform that work. PowerShell logs on multiple streams - DEBUG, VERBOSE, INFO (stdout), WARN, and ERROR (stderr) streams. However, when it exits and needs to provide those logs back to an exe (like choco.exe), it needs to combine those streams together as there is only stdout and stderr. You can probably guess what it does with DEBUG, VERBOSE, and WARN - straight to stderr, which makes it appear that there is an error that occurs when it is in fact just capturing the logs. Having it come back in CLIXML is also not helpful to deduce this is not an issue. We need to find a better way to log that.

[majkinetor]

This explains why AU fails when inserting certificate. I had to find a way to not execute that func within au updater

[ferventcoder]

To note, this may be something in SMA doing this. Still need to find a way to identify why it logs to stderr

[ferventcoder]

This is somewhat handled by #1126 - meaning it will just run the powerShell block when the process is already elevated.

[ferventcoder]

With the partial handling on this, I don't feel comfortable providing a fix for this without more testing time. Bumping to next release.

[pascalberger]

@ferventcoder Any progress on this? Or any workaround available?

The problem with this is that eg the yarn package always outputs error and we're in the process of rolling out this package company wide, which will lead to people believing that the installation was not successful even though it was.

[bcurran3]

Would a change in the package chocolateyinstall.ps1 to:
Start-ChocolateyProcessAsAdmin -Statements $script -ea SilentlyContinue
or
Start-ChocolateyProcessAsAdmin -Statements $script | out-null
work?

[ferventcoder]

@bcurran3 not really an option - both of those have different implementations - if there is an error we want to know. If we don't output any of the output and there is an issue, it will be invisible to the user. The problem is much of that falls in the verbose/debug/warn streams and outside of PowerShell, it doesn't know how to put that into stdout, so it shoves all of those into stderr. Quite annoying behavior. We need a way to redirect some streams to stdout (and I have tried to use redirection as part of the call to PowerShell, it didn't like it).

[nascentt]

It's been nearly four years.

Any progress on this?

[naveen521kk]

Possible workaround.
Let powershell log everything to a file. And choco reading those logs and appending it to choco log instead of reading the stout and stderr, after the process is over. Finally, showing the INFO messages to output.

[karol-pawlowski]

4 years and the issue is still there. Maybe one day you beat Atlassian with starved backlog :)