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
[Bug]: outdated / mismatched a2a.proto on grpc spec for compat-0.3 #1158
This is the Part definition in compat-0.3/spec-grpc/src/main/proto/a2a.proto. It seems to be missing the optional metadata field, according to python's a2a sdk for compat-0.3 there is a
java (compat-0.3/spec-grpc/src/main/proto/a2a.proto)
message Part {
oneof part {
string text = 1;
FilePart file = 2;
DataPart data = 3;
}
}
python (src/a2a/compat/v0_3/a2a_v0_3.proto)
message Part {
oneof part {
string text = 1;
FilePart file = 2;
DataPart data = 3;
}
// Optional metadata associated with this part.
google.protobuf.Struct metadata = 4;
}
This results in the SDK failing to parse the metadata field from responses that includes it.
Activity
kabir commentedon Sep 18, 2026
I don't know what a2a-python has done, but the spec version of the 0.3 a2a.proto is here: https://github.com/a2aproject/A2A/blob/v0.3.0/specification/grpc/a2a.proto
This is the one implementations should be aligned with, so I think what you are describing is probably a bug in a2a-python?
charmaineet commentedon Sep 18, 2026
I think this is the protocol definition on https://a2a-protocol.org/v0.3.0/specification/, so I think the python one should be correct? the metadata field is an optional field
kabir commentedon Sep 22, 2026
@charmaineet Thank you for the clarification. It isn't the first time the 0.3 spec and proto have been out of sync ;-)
Does #1169 meet your needs?
charmaineet commentedon Sep 23, 2026
@kabir thanks for the fix, yes it does!
charmaineet commentedon Sep 24, 2026
@kabir Can we have this merge released in a week if possible? Thank you so much!
kabir commentedon Sep 25, 2026
@charmaineet Will do one early next week :-)