Repository navigation
[Bug]: v0.3 REST client raises NotImplementedError for list_task_push_notification_configs #1423
Description
What happened?
Client.list_task_push_notification_configs() raises NotImplementedError when the client talks to a v0.3 agent over HTTP+JSON:
NotImplementedError: list_task_push_notification_configs not supported in v0.3 REST
The v0.3 REST binding defines this call as GET /v1/tasks/{id}/pushNotificationConfigs, and v0.3 REST servers serve it. That includes this SDK's own compat server: REST03Adapter mounts the route and REST03Handler.list_push_notifications handles it. The v0.3 JSON-RPC and gRPC client transports (CompatJsonRpcTransport, CompatGrpcTransport) both implement the call, so only REST users hit the error.
Steps to reproduce
- Start a server with
create_rest_routes(handler, enable_v0_3_compat=True)and a push config store. - Create a task and two push notification configs through
CompatRestTransport. - Call
CompatRestTransport.list_task_push_notification_configs(ListTaskPushNotificationConfigsRequest(task_id=...)).
Expected: the response lists both configs. Actual: NotImplementedError, and no request is sent.
Environment
a2a-sdk main (1.3.x), Python 3.13.
Activity
rohityan commentedon Nov 4, 2026
Hi @RaphaelFakhri, thanks for reporting this and opening PR #1424
Your root cause analysis is correct
CompatRestTransport.list_task_push_notification_configswas indeed left stubbed withNotImplementedError, even thoughGET /v1/tasks/{id}/pushNotificationConfigsis formally mounted on the v0.3 server adapter and implemented across the sibling transports.Your implementation in PR #1424 correctly executes the route via
_execute_request, parses the response proto, and threads it throughconversions.to_core_list_task_push_notification_config_responsewith matching test coverage.Assigning this issue to you till it gets reviewed.
fix(compat): list push notification configs in the v0.3 REST client (a…