{"version":"2.1.234","anchor":"a-failed-write-to-a-subprocess-s-stdin-no-longer-looks-like-","canonical_anchor":"a-failed-write-to-a-subprocess-s-stdin-no-longer-looks-like-","heading":"A failed write to a subprocess's stdin no longer looks like success","tier":"notice","area":"Shell Execution","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/a-failed-write-to-a-subprocess-s-stdin-no-longer-looks-like-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### A failed write to a subprocess's stdin no longer looks like success\n\nA command that fails while receiving input now reports an error instead of pretending it succeeded.\n\n**What**\n\nIf 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.\n\n**Details**\n\n- The failure is recorded as the reason the output was truncated, and the error text begins \"stdin write failed: \".\n\n**Evidence**\n\n`stdin write failed: `\n\n- Area: Shell Execution\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}