[Bug]: ListTasksResult rejects valid responses when pageSize ≠ number of returned tasks (InvalidParamsError)

オープン
  • 何か問題がありますか？
#1,260 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@RaphaelFakhri がすでに取り組んでいます。

2026年11月2日 から。

  • #1273 @RaphaelFakhri による — オープン

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
25/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
java, json
領域
api

調査の方向性

The strict check is in the compact constructor of jsonrpc-common/src/main/java/org/a2aproject/sdk/jsonrpc/common/wrappers/ListTasksResult.java; the error surfaces through ProtoUtils.FromProto.convert in the grpc utils. Pull request #1273 is already open against this issue, so review or build on that work rather than starting a parallel fix. Done means a response with pageSize 50 and 2 tasks parses into a ListTasksResult, with a test covering that case.

索引モデルが issue の本文から書いたものです。

説明

What happened?

Component: jsonrpc-common (ListTasksResult), reached via the JSON-RPC client transport

Version: a2a-java-sdk-client 1.4.0.Final (JSON-RPC transport)

What happened

Client.listTasks(...) fails with InvalidParamsError whenever the server's response has a pageSize that differs from the number of tasks in tasks. In practice this is every page that isn't completely full.

org.a2aproject.sdk.spec.InvalidParamsError: pageSize must be equal to the number of tasks in the list. Got 50, but list has 2 tasks.
    at org.a2aproject.sdk.grpc.utils.ProtoUtils$FromProto.convert(ProtoUtils.java:200)
    at org.a2aproject.sdk.grpc.utils.ProtoUtils$FromProto.listTasksResult(ProtoUtils.java:344)
    at org.a2aproject.sdk.grpc.utils.JSONRPCUtils.parseResponseBody(JSONRPCUtils.java:325)
    at org.a2aproject.sdk.client.transport.jsonrpc.JSONRPCTransport.unmarshalResponse(JSONRPCTransport.java:369)
    at org.a2aproject.sdk.client.transport.jsonrpc.JSONRPCTransport.listTasks(JSONRPCTransport.java:181)
    at org.a2aproject.sdk.client.Client.listTasks(Client.java:408)
    at org.a2aproject.sdk.client.AbstractClient.listTasks(AbstractClient.java:213)
Steps to reproduce
  1. Run an A2A server whose ListTasks response returns the requested page size in pageSize. The Python a2a-sdk 1.1.2 InMemoryTaskStore and DatabaseTaskStore do this (page_size = params.page_size or 50, returned as-is).
  2. Create 2 tasks in one contextId.
  3. Call client.listTasks(ListTasksParams.builder().contextId(ctx).pageSize(50).build()).

The server responds with this (abridged):

{"jsonrpc":"2.0","id":"1","result":{"tasks":[{...},{...}],"nextPageToken":"","pageSize":50,"totalSize":2}}
Expected behaviour

The response parses into a ListTasksResult with 2 tasks.

Actual behaviour

InvalidParamsError, thrown from the ListTasksResult compact constructor:

if (pageSize != tasks.size()) {
    throw new IllegalArgumentException("pageSize must be equal to the number of tasks in the list. Got " + pageSize + ", but list has " + tasks.size() + " tasks.");
}

(jsonrpc-common/src/main/java/org/a2aproject/sdk/jsonrpc/common/wrappers/ListTasksResult.java)

Why this looks like an SDK bug

The A2A specification, §3.1.4 List Tasks, says:

  • Request pageSize: "The maximum number of tasks to return. The service may return fewer than this value."
  • Response pageSize: "The page size used for this response."

A server may therefore return fewer tasks than pageSize, and the response pageSize is the page size applied rather than the count of tasks returned. The strict equality check rejects responses the spec allows.

Suggested fix
  • Remove the pageSize != tasks.size() check. Keep pageSize >= 0 if wanted.
  • Optionally, if the intent really is "count returned", the spec wording for the response pageSize should be clarified. Either way the SDK and the spec should agree.
Workaround

I currently rewrite result.pageSize to tasks.length in a decorating A2AHttpClient before the SDK parses the response.

Relevant log output
org.a2aproject.sdk.spec.InvalidParamsError: pageSize must be equal to the number of tasks in the list. Got 50, but list has 2 tasks.
    at org.a2aproject.sdk.grpc.utils.ProtoUtils$FromProto.convert(ProtoUtils.java:200)
    at org.a2aproject.sdk.grpc.utils.ProtoUtils$FromProto.listTasksResult(ProtoUtils.java:344)
    at org.a2aproject.sdk.grpc.utils.JSONRPCUtils.parseResponseBody(JSONRPCUtils.java:325)
    at org.a2aproject.sdk.client.transport.jsonrpc.JSONRPCTransport.unmarshalResponse(JSONRPCTransport.java:369)
    at org.a2aproject.sdk.client.transport.jsonrpc.JSONRPCTransport.listTasks(JSONRPCTransport.java:181)
    at org.a2aproject.sdk.client.Client.listTasks(Client.java:408)
    at org.a2aproject.sdk.client.AbstractClient.listTasks(AbstractClient.java:213)
Code of Conduct
  • I agree to follow this project's Code of Conduct
主要言語
Java
スター
510
フォーク
196
平均マージ
2日 22時間
マージ済み PR（30日）
31

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

a2aproject/a2a-java のほかの issue

a2aproject/a2a-java の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。