You'll notice
Useful3 Signal1
A command that floods its output is now reported as truncated instead of looking like a crash.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a spawned command exceeds the output buffer limit, the helper that runs it now returns an explicit overflow marker alongside the exit code instead of a generic failure, so the code that called it can tell truncated output apart from a crashed command.
Evidence
execFileNoThrow maxBuffer exceeded
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.234
Every session now gets the
cdpermission warning in the Bash toolBoth mention bash tool
-
v2.1.234
Command lessons are recorded with the command that produced them
Both mention bash tool
-
v2.1.238
Directory tracking for backgrounded commands no longer breaks early
Both mention bash tool