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
v0.3 REST server rejects a push config set without parent in the body #1498
The v0.3 spec gives the REST body for POST /v1/tasks/{id}/pushNotificationConfigs as { config: TaskPushNotificationConfig }, with the task in the path. a2a-python's v0.3 REST server rejects that body with 400 INVALID_ARGUMENT "No task for ". It only accepts the body if a redundant parent: "tasks/{id}" is included, which is what a2a-python's own client happens to send. JSON-RPC set works with the same config, and a2a-go's v0.3 server takes the task from the path.
Hi @ConnorMoss02, Thanks for reporting this. I was able to reproduce the issue.
In REST03Handler.set_push_notification(), the request body is parsed into CreateTaskPushNotificationConfigRequestand immediately passed to FromProto.task_push_notification_config_request() before task_id from request.path_params['id'] is assigned. Because parent is empty, TASK_NAME_MATCH fails and raises InvalidParamsError .
Thanks for contributing towards a fix in PR #1500 , it appears to resolve the issue. Assigning the issue to you till the PR is reviewed. Till then as a workaround callers on unpatched v0.3 servers can include the redundant "parent": "tasks/{task_id}" field in the JSON request body alongside "config".
Activity
rohityan commentedon Nov 19, 2026
Hi @ConnorMoss02, Thanks for reporting this. I was able to reproduce the issue.
In
REST03Handler.set_push_notification(), the request body is parsed intoCreateTaskPushNotificationConfigRequestand immediately passed toFromProto.task_push_notification_config_request()beforetask_idfromrequest.path_params['id']is assigned. Becauseparentis empty,TASK_NAME_MATCHfails and raisesInvalidParamsError.Thanks for contributing towards a fix in PR #1500 , it appears to resolve the issue. Assigning the issue to you till the PR is reviewed. Till then as a workaround callers on unpatched v0.3 servers can include the redundant
"parent": "tasks/{task_id}"field in the JSON request body alongside"config".