Skip to content

fix(automation): return a failing exit code on runner errors - #11964

Open
embrace897 wants to merge 1 commit into
deepflowio:mainfrom
embrace897:codex/main-runner-error-exit
Open

embrace897 wants to merge 1 commit into
deepflowio:mainfrom
embrace897:codex/main-runner-error-exit

Conversation

@embrace897

Copy link
Copy Markdown

The Socket.IO runner error callback raises an assertion on a background thread. The client can still exit with status 0 after disconnecting, so the workflow step can report success when the runner sends an error.

Record the failure before disconnecting and return a nonzero exit status from the main thread after the wait completes.

Validated with a local Socket.IO server and the pinned client dependencies. The original client exits 0 on an error. The patched client exits 1 on an error and 0 on a finish event. The hosted workflow was not run.

Prepared with AI assistance.

This branch has not been deployed

No deployments
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