Repository navigation
fix(a2a): propagate transport, protocol and remote task failures as structured errors (issue #213) - #371
Open
XianReallyHot-ZZH wants to merge 1 commit into
Conversation
…tructured errors (issue agentic-ai-java#213)
6 tasks
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
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.
Contributing to ARGI: propagate A2A streaming and single-body transport, protocol and remote task failures as structured terminal errors (A2aTransportException/A2aProtocolException/A2aRemoteTaskException extending IllegalStateException for legacy catch compatibility) instead of error text followed by a normal done completion — SSE wire-format framing (comments/unknown fields ignored, multi-data lines joined, [DONE] or completed status terminates, missing terminal state fails), JSON-RPC error frames, corrupt frames and remote failed/canceled tasks (both status-update events and Task objects) surface through the existing GraphResponse.error channel with at most one terminal state and partial output identity preserved, error-looking remote body text never treated as a control signal (issue #213).