You'll notice
Useful3 Signal1
A command that fails while receiving input now reports an error instead of pretending it succeeded.
What's wrong with this entry?
Anonymous. No account, no email.
What
If writing input to a spawned command fails with an error outside the ignored set, the child is killed and the run returns exit code 1 with an explicit error, instead of returning whatever partial output had been collected.
Details
- The failure is recorded as the reason the output was truncated, and the error text begins "stdin write failed: ".
Evidence
stdin write failed:
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