Uh oh!
There was an error while loading. Please reload this page.
CxODEV-1730: StructuredErrorException + structured_error task-output contract - #216
Merged
Conversation
…put contract Adds a framework capability for workers to attach a sanitized, structured error classification to a failed task's output: - StructuredErrorException(code, reason, referenceError?) - StructuredError DTO and ErrorOutput.StructuredError (omitted when null → back-compat) - StructuredErrorSerializer: OutputKey, ToOutputData (for signal senders) and tolerant TryParse (consumer side); a round-trip contract test pins the shape/key - both ExecutionManager and TypePollSpreadingExecutionManager populate structured_error when a StructuredErrorException is caught; plain exceptions still emit only error_message - version bumped 3.7.3 -> 3.8.0 (additive, on the v3 line) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Adds a framework capability for workers to attach a sanitized, structured error classification to a failed task's output, on the
v3line (3.7.3 → 3.8.0).StructuredErrorException(code, reason, referenceError?)StructuredErrorDTO +ErrorOutput.StructuredError(omitted when null → backward-compatible)StructuredErrorSerializer:OutputKey,ToOutputData(for signal senders) and tolerantTryParse(consumer side)ExecutionManagerandTypePollSpreadingExecutionManagerpopulatestructured_errorwhen aStructuredErrorExceptionis caught; plain exceptions still emit onlyerror_message(back-compat)Why
Part of CxODEV-1730 (persist ROM order failure details and propagate a sanitized classification to SOM). This is the transport layer the ROM/SOM engines build on.
Tests
StructuredErrorExceptionyieldsstructured_error(code/reason/reference_error/version) anderror_messagein the failed task output.Base is
v3(the 3.7.x maintenance line);master(4.x) is intentionally not targeted.🤖 Generated with Claude Code