推理流看起来“卡住”时：启用部分流保留并做重试信号去重回归
问题/场景：启用 reasoning 流时，用户端可能感知到输出中断或重复结束信号。前置：版本包含 PR #20635 修复。实施步骤：升级后对长推理场景做流式回归，检查 partial 持续输出、end 信号去重和重试后错误清理。关键命令：`openclaw gateway status`、`openclaw gateway restart`。验证：长推理期间 UI 持续有增量输出，重试后不残留旧错误。风险：不同客户端对 stream event 渲染行为可能不同。来源：GitHub PR + release notes 交叉整理。
GITHUBDiscovered 2026-02-21Author obviyus
Prerequisites
- Your deployment can be upgraded to a build that includes PR #20635.
- You have at least one channel/client where streaming behavior can be observed end-to-end.
Steps
- Upgrade runtime and restart gateway, then confirm baseline health before tests.
- Run a long reasoning prompt and record whether assistant partial output keeps updating continuously.
- Force one same-target retry after a controlled tool error and verify stale mutating errors are cleared.
- Check stream-end signaling appears once (no duplicate end state events in UI/logs).
Commands
openclaw gateway statusopenclaw gateway restartopenclaw statusVerify
In repeated long-stream tests, partial output remains live and retry flows no longer surface stale errors.
Caveats
- Client-side buffering can still make streams look bursty even when backend events are correct.
- Exact event names may evolve across versions; confirm against your installed release notes（需验证）.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗