Fix powershell streams leaking to standard error #19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Powershell has several streams. Unless, output is sent to the output stream, winrm interprets the output as error output. There are some module auto loading scenarios where powershell will send information out to the
progress
stream. This suppresses that stream all together by turning it off.Also, the checksum script currently writes the hash using
write-host
. As of powershell v5, output sent usingwrite-host
directs some metadata to a newinformation
stream and suffers the same problem as theprogress
stream where it causes winrm to leak to standard error. This simply replaceswrite-host
withwrite-output
which will be output to stdout and the console.This fixes #18