lhk229
fc53ee5c9c
Project CI / Frontend tests (pull_request) Failing after 27s
Project CI / Repository checks (pull_request) Failing after 54s
Project CI / Backend tests (pull_request) Successful in 4m55s
Project CI / Native shell tests (pull_request) Failing after 8m17s
补齐 Responses 的 incomplete 终态
Responses 的整体收尾信号有两个，此前只处理了 completed，incomplete 落入
通配分支被整个忽略。真实端点抓包确认：撞到 max_output_tokens 时上游只发
response.incomplete、不发 completed，载荷与 completed 同构，带完整 output[]，
item 标 status=incomplete，incomplete_details.reason 给出原因。
忽略它造成三件事：不终止读取循环，网关不主动关连接就等到调用方超时；流式
Responses 永远产生不出 incomplete 这个 finish_reason，上一轮加的截断拒绝规则
对它形同虚设；completed-only 型网关的工具调用被静默丢掉。
与 completed 合并到同一分支，只在 finish_reason 上区分。incomplete 由此自动
走 reject_incomplete_tool_calls：工具调用拒绝，正文按降级结果返回，与 Chat 的
length 口径一致。
三个用例的事件序列转录自真实抓包，退回通配分支时三条全部失败。
2026-07-27 08:51:53 +00:00
..
2026-07-23 10:50:02 +08:00
2026-07-03 15:19:44 +08:00
2026-07-16 18:33:06 +08:00
2026-07-08 21:35:02 +08:00
2026-05-22 05:00:07 +08:00
2026-05-16 22:52:10 +08:00
2026-05-15 06:24:07 +08:00
2026-05-16 22:52:10 +08:00
2026-05-21 20:20:06 +08:00
2026-07-17 21:03:15 +08:00
2026-05-15 06:24:07 +08:00
2026-06-12 22:42:39 +08:00
2026-05-22 03:06:41 +08:00
2026-05-07 21:11:14 +08:00
2026-05-15 06:24:07 +08:00
2026-06-11 23:06:41 +08:00
2026-06-03 22:11:46 +08:00
2026-05-15 06:24:07 +08:00
2026-07-14 19:20:25 +08:00
2026-05-15 06:24:07 +08:00
2026-05-22 03:14:11 +08:00
2026-05-07 21:11:14 +08:00
2026-05-07 21:11:14 +08:00
2026-05-16 22:52:10 +08:00
2026-05-21 23:34:07 +08:00
2026-07-13 16:26:27 +08:00
2026-07-21 19:40:38 +08:00
2026-07-13 22:06:36 +08:00
2026-07-14 20:30:44 +08:00
2026-07-20 16:08:24 +08:00
2026-05-27 21:57:34 +08:00
2026-07-21 19:40:38 +08:00
2026-07-27 08:51:53 +00:00
2026-07-18 21:17:35 +08:00
2026-07-04 12:03:58 +08:00
2026-05-10 13:18:46 +08:00
2026-07-14 12:16:01 +08:00
2026-06-11 22:33:05 +08:00
2026-07-21 19:40:38 +08:00
2026-07-16 18:33:06 +08:00
2026-05-22 03:06:41 +08:00
2026-07-18 12:22:58 +08:00
2026-07-21 19:40:38 +08:00
2026-05-06 12:52:47 +08:00