{"version":"2.1.239","anchor":"terminal-writes-are-timed-and-a-dead-stdout-no-longer-throws","canonical_anchor":"terminal-writes-are-timed-and-a-dead-stdout-no-longer-throws","heading":"Terminal writes are timed, and a dead stdout no longer throws","tier":"notice","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/terminal-writes-are-timed-and-a-dead-stdout-no-longer-throws","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Terminal writes are timed, and a dead stdout no longer throws\n\nTerminal writes are timed, and a broken output pipe marks the terminal dead instead of crashing.\n\n**What**\n\nEvery write to the terminal is timed and the slowest one is kept for later inspection, and where configured, an EIO or EPIPE error marks stdout dead instead of raising. Byte counts are reported back to the code that commits output.\n\n**Evidence**\n\n`tolerateDeadStdout`\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}