1 Commits

• include fractional portion of chunk that exceeds stdout/stderr limit (#497)

  I saw cases where the first chunk of output from `ls -R` could be large
  enough to exceed `MAX_OUTPUT_BYTES` or `MAX_OUTPUT_LINES`, in which case
  the loop would exit early in `createTruncatingCollector()` such that
  nothing was appended to the `chunks` array. As a result, the reported
  `stdout` of `ls -R` would be empty.
  
  I asked Codex to add logic to handle this edge case and write a unit
  test. I used this as my test:
  
  ```
  ./codex-cli/dist/cli.js -q 'what is the output of `ls -R`'
  ```
  
  now it appears to include a ton of stuff whereas before this change, I
  saw:
  
  ```
  {"type":"function_call_output","call_id":"call_a2QhVt7HRJYKjb3dIc8w1aBB","output":"{\"output\":\"\\n\\n[Output truncated: too many lines or bytes]\",\"metadata\":{\"exit_code\":0,\"duration_seconds\":0.5}}"}
  ```

  Michael Bolin · 2025-04-21 19:06:03 -07:00
  3eba86a553