Skip to content

fix(sessionservice): include subprocess stderr in FAILED lifecycle_detail#270

Draft
tildesrc wants to merge 1 commit into
mainfrom
panopticon/include-stderr-in-spawner-failed-detail
Draft

fix(sessionservice): include subprocess stderr in FAILED lifecycle_detail#270
tildesrc wants to merge 1 commit into
mainfrom
panopticon/include-stderr-in-spawner-failed-detail

Conversation

@tildesrc

@tildesrc tildesrc commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Summary

  • _subprocess_run in local_runner.py now catches CalledProcessError on the non-interactive/non-verbose path and re-raises as RuntimeError with the captured stderr included in the message
  • When docker run or docker build fails (e.g. bad --env-file path, image not found), the dashboard detail pane now shows the actual error from Docker rather than just "Command 'docker' returned non-zero exit status 125"
  • Two new unit tests cover the stderr-surfacing path and the no-stderr edge case

Plan: panopticon://tasks/4c5ebbe1a7d54b00af0e74e621208a66/artifacts/plan.md

🤖 Generated with Claude Code

…tail

When docker run/build fails, the CalledProcessError only surfaced the
exit code in the detail pane. Now _subprocess_run re-raises as RuntimeError
with the captured stderr so the dashboard shows the actual error message.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.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