Skip to content

v0.3 REST server rejects a push config set without parent in the body #1498

Description

@ConnorMoss02

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.

Activity

  1. added theissue type on Nov 19, 2026
  2. rohityan commented on Nov 19, 2026

    @rohityan

    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".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

component: serverIssues related to frameworks for agent execution, HTTP/event handling, database persistence logic.status:awaiting response

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions