You'll notice
Useful3 Signal1
A hook that dumps huge output now gives you a readable error instead of a wall of text.
What's wrong with this entry?
Anonymous. No account, no email.
What
Oversized hook output and error stacks are now cut down the middle with a marker saying how many characters were removed, so a hook that dumps a large stdout produces a readable failure instead of a wall of text.
Details
- The count in the marker accounts for characters already elided by nested markers, so it stays accurate.
- Errors are formatted as name and message plus at most five stack frames, each clipped to a line length.
- Applied to worktree-create hook failure output.
Evidence
characters truncated
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
SessionEnd hooks lose the
bypass_permissions_disabledreasonBoth mention hook
-
v2.1.236
Hooks and Ctrl-C go quiet once shutdown has started
Both mention hook
-
v2.1.236
Shutdown seals transcript writes and gives SessionEnd hooks more time
Both mention hook