Errors writing to a spawned command's input now surface instead of quietly truncating output.
What's wrong with this entry?
Child processes spawned through the exec helper now get an error listener on stdin. EPIPE, ECONNRESET and EOF are ignored as normal; any other error records the code, kills the child, and makes the call return exit code 1 with an error naming the failure.
- Applies to the non-throwing exec helper (
execFileNoThrow), which previously handed back a partial result in this case.
execFileNoThrow
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.227
Shell commands can run with credentials stripped from the environment
Both mention shell execution
-
v2.1.239
Remote tool execution is complete but hard-disabled in this build
Both mention execution
-
v2.1.239
The
deviceparameter is hidden from every tool that could run remotelyBoth mention execution