You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3ce65c5
Browse filesBrowse the repository at this point in the historyBrowse files
fix(errors): emit JSON-RPC error.data as typed-details array per A2A 1.0 spec hot-fix (a2aproject#1058)
# Description
Aligns the JSON-RPC and REST transports with the A2A 1.0 spec hot-fix
which makes `error.data` (JSON-RPC) and
`error.details` (REST) carry an array of typed-detail objects using the
ProtoJSON `Any` representation.
## Server side
`build_error_response` and `build_rest_error_payload` now emit a leading
`google.rpc.ErrorInfo` carrying the canonical A2A reason and
`error.data` as `metadata`. For `InvalidParamsError` with validation
details, both transports also append a `google.rpc.BadRequest`
## Client side
The JSON-RPC client now extracts `ErrorInfo.metadata` from the array
onto `A2AError.data`.
Also adds the missing `JSONParseError(-32700)` exception class so
JSON-RPC clients receive a typed exception for the standard parse-error
code instead of falling back to a generic `A2AClientError`.
Fixesa2aproject#1027. 🦕
0 commit comments