{"version":"2.1.239","anchor":"oversized-bash-output-is-marked-as-truncated-instead-of-quie","canonical_anchor":"oversized-bash-output-is-marked-as-truncated-instead-of-quie","heading":"Oversized Bash output is marked as truncated instead of quietly cut","tier":"notice","area":"Bash Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/oversized-bash-output-is-marked-as-truncated-instead-of-quie","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Oversized Bash output is marked as truncated instead of quietly cut\n\nBash output past the 10 MiB cap is now labelled truncated instead of quietly disappearing.\n\n**What**\n\nWhen a command's output passes the 10 MiB accumulation cap, the result is now flagged as truncated rather than silently losing the excess, and one more form of buffer-overflow error is recognised as such.\n\n**Details**\n\n- The result records `stdoutTruncated` once the cap is hit.\n- The overflow detector now also matches errors named `MaxBufferError`, in addition to the existing `ERR_CHILD_PROCESS_STDIO_MAXBUFFER` and max-buffer checks.\n\n**Evidence**\n\n`stdoutTruncated`\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}