[GH-ISSUE #179] native: expose output truncation metadata in command capture result #125

Closed
opened 2026-10-15 18:21:21 +00:00 by bsakaguchi · 1 comment
Owner

Originally created by @morluto on GitHub (Jul 14, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/179

Problem

stdoutTruncated and stderrTruncated in NativeCommandCapture are always false on successful captures.

Evidence

  • src/native/CommandRunner.ts:238-239 hard-codes both fields to false in the success path.
  • Capturing logic tracks an output-limit reason internally, but truncation status is not carried into the returned capture metadata.

Impact

Consumers cannot determine whether outputs were truncated once command output policy changes or future paths return partial captures.

Ask

Populate these flags based on process capture outcome, or adjust the type/API to remove/relocate truncation state if truncation is guaranteed to be an error-only path.

Originally created by @morluto on GitHub (Jul 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/179 ### Problem `stdoutTruncated` and `stderrTruncated` in `NativeCommandCapture` are always false on successful captures. ### Evidence - `src/native/CommandRunner.ts:238-239` hard-codes both fields to `false` in the success path. - Capturing logic tracks an `output-limit` reason internally, but truncation status is not carried into the returned capture metadata. ### Impact Consumers cannot determine whether outputs were truncated once command output policy changes or future paths return partial captures. ### Ask Populate these flags based on process capture outcome, or adjust the type/API to remove/relocate truncation state if truncation is guaranteed to be an error-only path.
bsakaguchi 2026-10-15 18:21:21 +00:00
Author
Owner

@morluto commented on GitHub (Jul 14, 2026):

Duplicate: superseded by #176 (same NativeCommandCapture truncation metadata gap).

<!-- gh-comment-id:4965879803 --> @morluto commented on GitHub (Jul 14, 2026): Duplicate: superseded by #176 (same NativeCommandCapture truncation metadata gap).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#125
No description provided.