bug: a2a send exits 0 when the task fails or needs input, and a timeout hides the task ID

未关闭
#136 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
68/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
go
领域
cli

调研方向

Start by tracing the a2a send command’s task status handling, timeout error path, and existing exit code tests; the issue names no files or test commands. Check how failed, rejected, canceled, and input-required statuses are reported, then verify the timeout path preserves a task ID when the server returned one. Done means scripts receive distinct non-zero exit codes for the specified terminal failures and timeout errors include the available task ID.

由索引模型根据 Issue 内容生成。

描述

bug

Scripts can't tell from the exit code whether a task worked.

  • a2a send exits 0 when the task ends failed, for example a2a send -a $U "" ; echo $? against a2a-serve, or a task whose agent crashed.
  • It also exits 0 when the task ends input-required, and with --stream it ends on the status line with no hint on how to answer.
  • When --timeout expires, the error is context deadline exceeded with no task ID, so the caller can't follow or cancel the task it started. The Resume: a2a send --task-id line only appears for input-required tasks.

Expected: distinct non-zero exit codes for failed, rejected and canceled (and optionally one for input-required/auth-required), and the task ID in the timeout error when the server returned one.

Seen with a2a v0.4.0.

Found by user simulation (tools/sim) at a2a-serve 1994e97.

主要语言
Go
星标
181
派生
28
平均合并
2 天 11 小时
30 天内合并 PR
22

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

a2aproject/a2a-cli 的其他 Issue

查看 a2aproject/a2a-cli 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。