Fix debug logger fallback to cap total output bytes#1907
Merged
Conversation
Replace `cut -c1-$MAX_OUTPUT` with `head -c $MAX_OUTPUT` so the 200KB cap applies to the entire output stream instead of truncating each line independently, which could allow multi-line input to exceed the intended limit. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
cut -c1-$MAX_OUTPUTwithhead -c $MAX_OUTPUTin the debug prompt logger's jq-missing fallback pathcut -ctruncates each line independently, so multi-line input could exceed the 200KB caphead -ctruncates the total byte stream, correctly enforcing the intended limitAddresses review feedback on #1902.