[Bug]: SendStreamingMessage returns an empty 200 stream when the executor produces no events

Open
#1,459 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 2 days

@rohityan is already working on this.

Since Nov 12, 2026.

  • #1460 by @1AbdullahButt — open

Assessment

This issue has not been assessed yet.

Description

What happened?

Since #1345, SendMessage with an AgentExecutor that returns without enqueueing any event fails with InvalidAgentResponseError ("Agent execution produced no events", JSON-RPC -32006). SendStreamingMessage with the same executor still answers 200 text/event-stream with zero events and closes, so the client gets no Task, no Message and no error.

Spec §3.1.2 says the stream MUST either contain exactly one Message, or begin with the Task: https://a2a-protocol.org/latest/specification/#312-send-streaming-message. An empty stream is neither, and the client can't tell it apart from a stream that closed early.

Code on main (2ba8e7b): on_message_send has the guard (https://github.com/a2aproject/a2a-python/blob/2ba8e7bd27fce7de92c33813a46dbea1e3f7e6ce/src/a2a/server/request_handlers/default_request_handler_v2.py#L522-L527); on_message_send_stream returns once subscribe() ends, whatever it yielded (https://github.com/a2aproject/a2a-python/blob/2ba8e7bd27fce7de92c33813a46dbea1e3f7e6ce/src/a2a/server/request_handlers/default_request_handler_v2.py#L547-L572).

Repro

import asyncio
from a2a.server.agent_execution import AgentExecutor
from a2a.server.context import ServerCallContext
from a2a.server.request_handlers import DefaultRequestHandler
from a2a.server.tasks import InMemoryTaskStore
from a2a.types.a2a_pb2 import AgentCapabilities, AgentCard, Message, Part, Role, SendMessageRequest

class SilentExecutor(AgentExecutor):
    async def execute(self, context, event_queue):
        return None
    async def cancel(self, context, event_queue):
        return None

def request():
    return SendMessageRequest(message=Message(message_id='m1', role=Role.ROLE_USER, parts=[Part(text='hi')]))

async def main():
    handler = DefaultRequestHandler(
        agent_executor=SilentExecutor(),
        task_store=InMemoryTaskStore(),
        agent_card=AgentCard(name='a', version='1', capabilities=AgentCapabilities(streaming=True)),
    )
    try:
        await handler.on_message_send(request(), ServerCallContext())
    except Exception as e:
        print('on_message_send        ->', type(e).__name__, e)
    events = [e async for e in handler.on_message_send_stream(request(), ServerCallContext())]
    print('on_message_send_stream ->', events)

asyncio.run(main())

Output on main:

on_message_send        -> InvalidAgentResponseError Agent execution produced no events
on_message_send_stream -> []

Over HTTP the same thing shows up as SendMessage returning a -32006 error, while SendStreamingMessage (JSON-RPC) and POST /message:stream (REST) return 200 with an empty event stream.

Expected: the streaming call fails the same way as the non-streaming one: InvalidAgentResponseError, which the JSON-RPC dispatcher and the REST dispatcher already turn into an error response because they read the first event eagerly.

Actual: an empty, successful stream.

I have a fix with a regression test and will open a PR.

Code of Conduct
  • I agree to follow this project's Code of Conduct
Dominant language
Python
Stars
2.2k
Forks
540
Avg merge
2d 9h
Merged PRs (30d)
56

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from a2aproject/a2a-python

All issues in a2aproject/a2a-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.