{{ message }}
Repository navigation
fix: UnsupportedOperationError gRPC status should be FAILED_PRECONDITION per spec #1051
Description
Problem
The A2A specification (section 5.4) defines the following gRPC status mapping for UnsupportedOperationError:
However, A2AErrorCodes.UNSUPPORTED_OPERATION in the SDK maps to UNIMPLEMENTED:
UNSUPPORTED_OPERATION(-32004, "UNIMPLEMENTED", 400),This diverges from the spec table, which says the gRPC status should be FAILED_PRECONDITION.
Expected behavior
UNSUPPORTED_OPERATION should map to gRPC FAILED_PRECONDITION to match the spec.
Context
Found during review of #1041, which correctly changed streaming-not-supported errors from InvalidRequestError to UnsupportedOperationError. The gRPC status mismatch is a pre-existing issue unrelated to that PR.
Activity
dangzitou commentedon Aug 12, 2026
I reproduced this on current
main(643f1f80). I updated only the existing gRPC assertions for paths that emitUnsupportedOperationErrorand ran:mvn -pl transport/grpc -am -Dtest=GrpcHandlerTest -Dsurefire.failIfNoSpecifiedTests=false testAll 8 affected paths failed consistently with
expected: <FAILED_PRECONDITION> but was: <UNIMPLEMENTED>(42 tests total, 34 unaffected tests passed). I am working on the minimal mapping/test/doc update.fix(grpc): align unsupported operation status
fix(grpc): align unsupported operation status
kabir commentedon Aug 19, 2026
Closing as per #1059 (comment)