fix(grpc): align unsupported operation status - #1059
Open
dangzitou wants to merge 1 commit into
Open
Conversation
dangzitou
marked this pull request as ready for review
August 12, 2026 19:54
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.
Description
Align
UnsupportedOperationErrorwith the A2A gRPC specification by mapping it toFAILED_PRECONDITIONinstead ofUNIMPLEMENTED. Update the existing server and client mapping assertions, plus the handler mapping documentation.CONTRIBUTINGGuide.Reproduction
On current
main, changing only the eight existingGrpcHandlerTestexpectations for paths that emitUnsupportedOperationErrorproduced 8 consistent failures out of 42 tests:Verification
Run with OpenJDK 17:
Results:
transport/grpc: 42 tests passedclient/transport/grpc: 9 tests passedA root
mvn clean installwas also attempted, but the unrelatedclient/transport/jsonrpctests could not bind/use their hard-coded local endpoint because127.0.0.1:4001was already occupied by another local application. The two changed gRPC modules were fully tested separately above.This fixes #1051