After a subscriptions/listen reconnect, how does a client learn about transitions it missed?
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Start with the cited task subscription requirements in specification/2026-07-28/tasks.md, then read the reconnection behavior in basic/patterns/subscriptions.mdx and the SSE note in changelog.mdx. Compare the server-side and client-side proposals, resolve which requirement the specification should adopt, and update the relevant task subscription text so missed transitions are handled after reconnecting.
由索引模型根据 Issue 内容生成。
描述
Context
notifications/taskscarries a completeDetailedTask, "identical to whattasks/getwould have returned at that moment" (specification/2026-07-28/tasks.md:477). Clients "MAY continue pollingtasks/getin addition to subscribing … but need not do so" (:505).- In core MCP 2026-07-28, an abrupt transport drop ends a subscription (
basic/patterns/subscriptions.mdx:125). The client "MAY treat [it] as a trigger to reconnect" (:157-158). On stdio it "MUST re-sendsubscriptions/listen", and the server "holds no subscription state across reconnections" (:160-162). - SSE resumability was removed on purpose in this revision (SEP-2575,
changelog.mdx:28). This issue doesn't ask to bring it back. Snapshot notifications make it unnecessary for tasks, with one exception, below.
The gap
A client that follows :505 and relies on notifications alone can do this:
subscriptions/listenwithtaskIds: [T], and the ack confirmsT.- The transport drops.
Tmovesworking → completed(or→ input_required) while no stream exists. The notification has nowhere to go.- The client reconnects and re-sends
subscriptions/listenforT, and the server acks. Tis terminal, so nothing further ever changes. The client never receives a notification and waits untilttlMsexpires.
For input_required, the task also stalls server-side, because the client never sees inputRequests.
Proposal (either line settles it)
- Server side: "After acknowledging a
subscriptions/listenthat includestaskIds, the server SHOULD send onenotifications/taskscarrying the currentDetailedTaskfor each acknowledged task ID." This is snapshot-on-subscribe, the same shape A2A'sSubscribeToTaskuses. - Client side: "A client that (re-)establishes a subscription MUST call
tasks/getonce for each task ID in the acknowledgement before relying on notifications alone." This needs no server change and fits the "need not poll" text as long as that text gets this qualifier.
lastUpdatedAt (tasks.md:133) already lets a client discard a stale snapshot if both a poll and a notification arrive, so either option is safe to combine with polling.
- 主要语言
- TypeScript
- 星标
- 52
- 派生
- 12
- 平均合并
- 4 天 23 小时
- 30 天内合并 PR
- 4
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
modelcontextprotocol/ext-tasks 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 82/100
-
enhancement
难度 2/5 1-3 小时 新手友好度 68/100
modelcontextprotocol/ext-tasks#22 · 1 条评论 ·
-
enhancement
难度 4/5 3-5 天 新手友好度 35/100
modelcontextprotocol/ext-tasks#30 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 45/100
modelcontextprotocol/ext-tasks#20 · 2 条评论 ·
查看 modelcontextprotocol/ext-tasks 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 77/100
apache/rocketmq-dashboard#6610 ·
维护者通常 3 天内回复
-
nextjs-tracking
难度 2/5 1-3 小时 新手友好度 69/100
cloudflare/vinext#3920 ·
维护者通常 1 天内回复
-
Team:Dashboards
难度 2/5 1-3 小时 新手友好度 65/100
elastic/kibana#297299 · 1 条评论 ·
维护者通常 1 天内回复
-
analytics beginner friendly community contributions-welcome good first issue hacktoberfest help wanted up-for-grabs
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
affected/v17 affected/v18 area/frontend type/bug
难度 2/5 1-3 小时 新手友好度 82/100
umbraco/Umbraco-CMS#24186 ·
维护者通常 2 天内回复