Fix error message at the end of each action run - #39
Merged
Conversation
Gobra runs in a container that the action's own container starts, so the runner's file commands are out of reach there: `GITHUB_OUTPUT` is not passed to the nested `docker run`, which made writing to it fail on every run, at first with "ambiguous redirect" and, since the expansion is quoted, now with "No such file or directory". Passing the variable through would not help either, since it holds a path that is only mounted into the outer container. The inner entrypoint now reports the time on stdout through `reportTime`, which both the config file mode failure path and the regular path use, and the outer entrypoint forwards it to `GITHUB_OUTPUT`, where that file is reachable, so the `time` output of the action is produced again. The exit code of `docker run` travels through a file because the pipe into `tee` would otherwise hide it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DcwZQqj9Vc8md7EUHK7nKL
`DEBUG_OUT` pointed at `/dev/nil`, so with debug output disabled every debug line was written to a regular file of that name instead of being discarded. `DEBUG_MODE` was also hardcoded to 0, which made the variable that the outer entrypoint passes into the container have no effect. It now defaults to 0 and can be enabled by setting it on the workflow step. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DcwZQqj9Vc8md7EUHK7nKL
jcp19
commented
Aug 10, 2026
The run that prints the resolved configuration happens before the time is measured, so the value reported when it fails carried no information. The `time` output is now simply left unset on that path, which also removes the only other place that wrote to `GITHUB_OUTPUT` from within the container. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DcwZQqj9Vc8md7EUHK7nKL
jcp19
commented
Aug 10, 2026
Restores `reportTime` and makes the line it prints readable, instead of the marker that only the outer entrypoint had a use for. The wording is now part of the interface between the two scripts, so both sides say so. The path that fails to print the resolved configuration states that nothing was verified and that no time is reported, rather than leaving the missing `time` output unexplained. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DcwZQqj9Vc8md7EUHK7nKL
jcp19
commented
Aug 10, 2026
jcp19
commented
Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the message
/gobra/entrypoint.sh: line 281: : No such file or directoryprinted at the end of each run.