Skip to content

fix: add fallback for RUNNER_TEMP to prevent undefined file path#88

Open
MaxwellCalkin wants to merge 1 commit intoanthropics:mainfrom
MaxwellCalkin:fix/runner-temp-fallback
Open

fix: add fallback for RUNNER_TEMP to prevent undefined file path#88
MaxwellCalkin wants to merge 1 commit intoanthropics:mainfrom
MaxwellCalkin:fix/runner-temp-fallback

Conversation

@MaxwellCalkin
Copy link
Copy Markdown

@MaxwellCalkin MaxwellCalkin commented Mar 8, 2026

Summary

When RUNNER_TEMP is not set (e.g., during local testing with test-local.sh or in non-standard CI environments), the execution file path resolves to the literal string "undefined/claude-execution-output.json", producing a confusing ENOENT error when the action tries to write the execution log.

Change: Falls back to /tmp when RUNNER_TEMP is unset, matching the behavior documented in CLAUDE.md ("Outputs execution logs as JSON to /tmp/claude-execution-output.json").

Before: RUNNER_TEMP unset → path is "undefined/claude-execution-output.json" → ENOENT error
After: RUNNER_TEMP unset → path is "/tmp/claude-execution-output.json" → works correctly

Test plan

  • All 118 existing tests pass
  • TypeScript typecheck passes
  • Verified process.env.RUNNER_TEMP || "/tmp" produces /tmp when unset

AI Disclosure

This PR was authored by Claude Opus 4.6 (Anthropic), an AI agent operated by Maxwell Calkin (@MaxwellCalkin).

When RUNNER_TEMP is not set (e.g., local testing or non-standard CI
environments), the execution file path resolves to the literal string
"undefined/claude-execution-output.json", causing a confusing ENOENT
error. Falls back to /tmp when RUNNER_TEMP is unset.

Co-Authored-By: Claude Opus 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