Skip to content

Raise a failed call's stderr from the entrypoint - #14

Draft
eunomie wants to merge 1 commit into
mainfrom
entrypoint-error-propagation
Draft

eunomie wants to merge 1 commit into
mainfrom
entrypoint-error-propagation

Conversation

@eunomie

@eunomie eunomie commented Nov 11, 2026

Copy link
Copy Markdown
Member

On engine beta.27 a failed exec's error message carries only exit code: 1, so a PHP function's error no longer reached the caller and generated-entrypoint-call-check fails on main (and on #11, #12, #13). The generated entrypoint now catches the exec's error and raises the stderr from its extensions (the engine caps it at 100 KiB), re-raising the original error when there is none. The exec keeps the default expect, so a failed exec is not cached and a retry runs again.

Checks, on the beta.27 engine and CLI: generated-entrypoint-call-check passed (it failed on main); sdk-unit-check and entrypoint-config-check passed on an earlier revision of this change (the final revision reran the call check; unit run could not be shown to execute PHPUnit).

The exec still fails, so the engine does not cache it and a retry runs
the function again; an exec with expect: ANY would replay the failure.

Signed-off-by: Yves Brissaud <yves@dagger.io>
@eunomie
eunomie force-pushed the entrypoint-error-propagation branch from 60cc17a to bdeaf20 Compare November 11, 2026 14:30
@eunomie
eunomie added this pull request to stack #32 November 11, 2026 14:32
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