Skip to content

cli: surface the review subprocess's stderr when it fails#233

Open
ftabba wants to merge 1 commit into
sashiko-dev:mainfrom
ftabba:pr/cli-stderr-on-failure
Open

cli: surface the review subprocess's stderr when it fails#233
ftabba wants to merge 1 commit into
sashiko-dev:mainfrom
ftabba:pr/cli-stderr-on-failure

Conversation

@ftabba

@ftabba ftabba commented Jun 1, 2026

Copy link
Copy Markdown

sashiko-cli local runs the review in a subprocess and streams its stderr only to drive the four-phase progress display, discarding every other line. When the subprocess failed before producing a result, the user saw only "Review subprocess produced no output (exit code: N)" with the actual cause (a stage error, an auth or quota failure, a panic) silently dropped.

Keep a bounded tail (the last 100 lines) of the subprocess's stderr while rendering progress, and replay it on the no-output failure path. Successful runs are unchanged (clean progress), while failures now explain themselves.

Assisted-by: Antigravity:gemini-3.1-pro
Signed-off-by: Fuad Tabba tabba@google.com

`sashiko-cli local` runs the review in a subprocess and streams its stderr only
to drive the four-phase progress display, discarding every other line. When the
subprocess failed before producing a result, the user saw only "Review
subprocess produced no output (exit code: N)" with the actual cause (a stage
error, an auth or quota failure, a panic) silently dropped.

Keep a bounded tail (the last 100 lines) of the subprocess's stderr while
rendering progress, and replay it on the no-output failure path. Successful runs
are unchanged (clean progress), while failures now explain themselves.

Assisted-by: Antigravity:gemini-3.1-pro
Signed-off-by: Fuad Tabba <tabba@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant