{"version":"2.1.284","anchor":"plugin-runtime-processrun-reports-output-truncation","canonical_anchor":"plugin-runtime-processrun-reports-output-truncation","heading":"Plugins can tell when output from a process they ran was cut off","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/plugin-runtime-processrun-reports-output-truncation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Plugins can tell when output from a process they ran was cut off\n\nThe plugin runtime's `$.process.run` now reports `isStdoutTruncated` and `isStderrTruncated` when output passes its 4 MiB limit\n\n**Unclear.** It is not clear whether the 4 MiB limit is also new or only the two truncation values are.\n\n**What**\n\nPlugins and hooks can start other programs with `$.process.run`. It keeps at most 4194304 bytes (4 MiB) of each output stream. Its result now includes two extra values:\n\n- `isStdoutTruncated`: true when the normal output was cut off\n\n- `isStderrTruncated`: true when the error output was cut off\n\nBefore this, the result held only the exit code and the two outputs, and nothing showed when text had been dropped.\n\n**Why**\n\nPlugin authors can now detect that they received only part of a program's output, instead of treating partial text as complete.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}