Read the dispatch mode from the event payload; name failure classes #2

Merged
ClaudiuSchuster merged 2 commits from oss-oo/publication-dispatch-fix into main 2026-09-23 02:23:41 +00:00
Owner

First dispatched plan run failed as a generic publication_failed: the runner rendered an empty inputs.mode expression. Derive the mode from the event payload JSON instead of the expression context, and include the exception class name in the sanitized generic failure so boundary failures stay diagnosable without leaking content. Local: py_compile, YAML parse, focused test groups green.

First dispatched plan run failed as a generic publication_failed: the runner rendered an empty inputs.mode expression. Derive the mode from the event payload JSON instead of the expression context, and include the exception class name in the sanitized generic failure so boundary failures stay diagnosable without leaking content. Local: py_compile, YAML parse, focused test groups green.
Read the dispatch mode from the event payload and name failure classes
Some checks failed
Repository checks / repository-baseline (pull_request) Failing after 7m44s
7fe45b44bc
The runner rendered an empty inputs.mode expression, so the dispatched
plan died as a generic publication_failed; derive the mode from the
event payload instead and include the exception class for boundary
failures so the sanitized report stays diagnosable.
CI: rerun after another runner recreate interrupted the suite
All checks were successful
Repository checks / repository-baseline (pull_request) Successful in 9m56s
6cd12b82e4
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
OSS-Singularity/website!2
No description provided.