Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Don’t parse the pipeline as text when it is directed from an EXE to another EXE or file. Keep the bytes as-is.

See original GitHub issue

Currently PowerShell parses STDOUT as string when piping from an EXE, while in some cases it should be preserved as a byte stream, like this scenario:

curl.exe http://whatever/a.png > a.png

node a.js | gzip -c > out.gz

Affected patterns include: native | native, native > file and (maybe) cat file | native.

Issue Analytics

State:
Created 7 years ago
Reactions:101
Comments:67 (4 by maintainers)

Top GitHub Comments

29reactions

SeeminglySciencecommented, Jun 5, 2023

Forgot to mark the PR as resolving this issue! The PR was merged on 04/27, should be in the next preview 🎉 Closing

Oh also when it does make it to preview, remember to run Enable-ExperimentalFeature PSNativeCommandPreserveBytePipe and file any feedback if you find issues ❤️

23reactions

SeeminglySciencecommented, Feb 10, 2023

Indeed, it’s the one thing stopping many Linux users from pwsh adoption as a primary shell. Has there been any progress on this front, pwsh team?

@potatoqualitee yeah, my PR is ready for review now (#17857). It is a large change in a sensitive area of the code base, so don’t expect a speedy review, but it’s comin’.