[Bug]: ListTasks prints unset fields on every task (history: [] with historyLength=0, empty mediaType/filename on parts)
I maintainer di solito rispondono entro 2 giorni
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
What happened?
ListTasks (JSON-RPC and REST) serializes its tasks differently from GetTask. serialize_list_tasks_response uses MessageToDict(..., always_print_fields_with_no_presence=True), which is there so nextPageToken, pageSize and totalSize are always present. But the flag applies to the whole tree, so every nested task, message and part also gets its unset fields printed as defaults:
Two visible effects on main (2ba8e7b):
- With
historyLength: 0, each task still carries"history": []. §3.2.4 says that for 0 "thehistoryfield SHOULD be omitted" (https://a2a-protocol.org/latest/specification/#324-history-length-semantics), andGetTaskdoes omit it. #1211 fixed the same thing forartifacts, by popping the key afterwards. - Messages and parts in a listed task get fields the stored task never had:
"filename": ""and"mediaType": ""on a text part,"contextId": "","taskId": "","extensions": []and"referenceTaskIds": []on a message. The same task fetched withGetTaskhas none of them, so one task has two JSON shapes depending on the method used to read it.
Repro (one stored task, real DefaultRequestHandler behind create_jsonrpc_routes):
import asyncio, json, httpx
from starlette.applications import Starlette
from a2a.server.context import ServerCallContext
from a2a.server.request_handlers import DefaultRequestHandler
from a2a.server.routes import create_jsonrpc_routes
from a2a.server.tasks import InMemoryTaskStore
from a2a.types.a2a_pb2 import AgentCard, Message, Part, Role, Task, TaskState, TaskStatus
async def main():
store = InMemoryTaskStore()
msg = Message(message_id='m1', role=Role.ROLE_USER, parts=[Part(text='hi')])
await store.save(Task(id='t1', context_id='c1', status=TaskStatus(state=TaskState.TASK_STATE_WORKING), history=[msg]), ServerCallContext())
handler = DefaultRequestHandler(None, store, AgentCard(name='a', version='1'))
app = Starlette(routes=create_jsonrpc_routes(handler, '/'))
async with httpx.AsyncClient(transport=httpx.ASGITransport(app=app), base_url='http://agent', headers={'A2A-Version': '1.0'}) as c:
async def call(method, params):
r = await c.post('/', json={'jsonrpc': '2.0', 'id': 1, 'method': method, 'params': params})
return r.json()['result']
print('GetTask historyLength=0:', json.dumps(await call('GetTask', {'id': 't1', 'historyLength': 0})))
print('ListTasks historyLength=0:', json.dumps((await call('ListTasks', {'historyLength': 0}))['tasks'][0]))
print('GetTask :', json.dumps((await call('GetTask', {'id': 't1'}))['history']))
print('ListTasks :', json.dumps((await call('ListTasks', {}))['tasks'][0]['history']))
asyncio.run(main())
Output on main:
GetTask historyLength=0: {"id": "t1", "contextId": "c1", "status": {"state": "TASK_STATE_WORKING"}}
ListTasks historyLength=0: {"id": "t1", "contextId": "c1", "status": {"state": "TASK_STATE_WORKING"}, "history": []}
GetTask : [{"messageId": "m1", "role": "ROLE_USER", "parts": [{"text": "hi"}]}]
ListTasks : [{"messageId": "m1", "role": "ROLE_USER", "parts": [{"text": "hi", "filename": "", "mediaType": ""}], "contextId": "", "taskId": "", "extensions": [], "referenceTaskIds": []}]
REST GET /tasks?historyLength=0 shows the same output, since both bindings use serialize_list_tasks_response.
Expected: each task in ListTasks serializes like the same task from GetTask: no history key for historyLength: 0, and no empty-default fields on messages and parts. Only the top-level response fields (tasks, nextPageToken, pageSize, totalSize) and, with includeArtifacts: true, artifacts need to be printed when empty.
Actual: history: [] with historyLength: 0, and empty-string or empty-list values on every nested message and part.
Happy to send a fix if that helps.
Code of Conduct
- I agree to follow this project's Code of Conduct
- Lingua principale
- Python
- Stelle
- 2.2k
- Fork
- 540
- Merge medio
- 2g 9h
- PR unite (30g)
- 56
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di a2aproject/a2a-python
-
[Bug]: `A2A-Version` validation ignores minor versions and the query parameterForse già presa @rohityan l’ha presa 82 giorni fa. Apertacomponent: server status:awaiting response status:stale
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
a2aproject/a2a-python#1204 · 4 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 2 giorni
-
[Bug]: REST task/request id sanitizationForse di nuovo libera Una pull request per questa issue è stata chiusa senza essere unita. Apertamaintainers-only
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
a2aproject/a2a-python#805 · 1 commento ·
I maintainer di solito rispondono entro 2 giorni
-
[Bug]: JSON-RPC client ignores the JSON-RPC error body when the HTTP status is not 2xxForse già presa @rohityan l’ha presa oggi. Aperta
a2aproject/a2a-python#1475 · 2 assegnatari ·
I maintainer di solito rispondono entro 2 giorni
-
[Feat]: validate_input_modes: match media ranges such as image/* declared in the agent cardForse già presa @rohityan l’ha presa 2 giorni fa. Aperta
a2aproject/a2a-python#1468 · 2 assegnatari ·
I maintainer di solito rispondono entro 2 giorni
-
Required extensions aren't enforced, so ExtensionSupportRequiredError is never raisedForse già presa @rohityan l’ha presa 2 giorni fa. Apertacomponent: server status:awaiting response
a2aproject/a2a-python#1467 · 1 commento · 1 assegnatario ·
I maintainer di solito rispondono entro 2 giorni
Tutte le issue di a2aproject/a2a-python
Issue simili
-
area:security effort:S priority:P3 status:needs-triage type:chore
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
randomparity/kdive#3657 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
aws/mcp-proxy-for-aws#476 ·
I maintainer di solito rispondono entro 1 giorno
-
fix(cli): a --root that does not exist exits 0 with 'Scanned 0 file(s)', so a wrong path in CI passes silentlyForse già presa @arpanjot-coding l’ha presa oggi. Apertaarea: runtime automation bug cli code-scanning consistency developer-experience difficulty: easy github-actions good first issue help wanted json-output priority: P3 python sarif silent-failure static-analysis tests
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
-
ContainsOnly raises TypeError for unhashable input with set-based choicesForse già presa @prathamchoksi l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
marshmallow-code/marshmallow#3115 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno