Skip to content

Return error instead of log.Fatalf in storage/cli_adaptor.go - #14

Merged
jim-junior merged 1 commit into
urunc-dev:mainfrom
magic-peach:fix/10-storage-cli-adaptor-no-fatal
Sep 18, 2026
Merged

jim-junior merged 1 commit into
urunc-dev:mainfrom
magic-peach:fix/10-storage-cli-adaptor-no-fatal

Conversation

@magic-peach

Copy link
Copy Markdown
Contributor

Description

Part of #10. Covers internal/runtime/storage/cli_adaptor.go: replaces the single log.Fatalf in CLIStartTask with a wrapped error, including captured stdout/stderr for parity with the JSON-parse error handling right below it.

Issues Resolved

Updates #10 (one of four small PRs against this issue, one per file)

Testing

go build, go vet, gofmt -l, go test ./... all clean.

log.Fatalf calls os.Exit(1) directly, which kills the whole harness
process on a single trial's nerdctl failure instead of letting the
orchestrator record the trial as failed and move on. CLIStartTask
already returns (StageResult, error) as part of its signature, so no
caller changes were needed: the fatal call is replaced with returning
the underlying error wrapped with fmt.Errorf, including the captured
stdout/stderr for debuggability, consistent with the JSON-parse error
returned a few lines below it in the same function.

Updates urunc-dev#10

Signed-off-by: Akanksha Trehun <akankshatrehun@gmail.com>

@jim-junior jim-junior left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

adding the standard output and stderror to error message is a good change

@jim-junior
jim-junior merged commit b72c586 into urunc-dev:main Sep 18, 2026
2 checks passed
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.

2 participants