Skip to content

[PR] feat(compress): add streamMarkers setting to suppress streaming receipts (#3906) - #4934

Closed
fathonix wants to merge 5 commits into
ranxianglei:masterfrom
fathonix:feat/stream-markers-setting
Closed

fathonix wants to merge 5 commits into
ranxianglei:masterfrom
fathonix:feat/stream-markers-setting

Conversation

@fathonix

Copy link
Copy Markdown
Contributor

PR 1: feat(compress): add streamMarkers setting to suppress streaming receipts (#3906)

Problem / Background

When streaming responses in client UI environments (e.g. OpenCode, Pi, Cursor), Billion-Context emits streaming visibility markers (📦 [ACP] Compressed ..., ❌ [ACP] ... FAILED) directly into response deltas so users can see compression actions in real-time.

However, in certain automated agent workflows, headless script harnesses, or strictly formatted markdown interfaces, injecting marker text deltas directly into the client stream can interfere with downstream parsers, pollute test suites, or create visual noise. Prior to this change, while visibilityMarkers controls overall marker generation, there was no granular toggle to suppress streaming receipt emission while keeping standard loop execution intact.

Changes

  • src/config.ts:
    • Added streamMarkers?: boolean to configuration schema and compress.streamMarkers configuration key.
    • Added environment variable fallback BILI_STREAM_MARKERS (defaulting to true to preserve backward compatibility).
  • src/compress-settings.ts:
    • Propagated streamMarkers through compression options resolution.
  • src/compress-loop-responses.ts:
    • Guarded streaming marker injection in emitStreamingMarker / receipt chunk creation when streamMarkers === false.
  • src/server/relay.ts:
    • Passed streamMarkers flag through runCompressLoop context.

Verification

  • Verified config parsing accepts compress.streamMarkers: false and BILI_STREAM_MARKERS=0.
  • Verified default behavior remains identical (streamMarkers: true emits receipts as before).
  • Verified with streamMarkers: false that compression completes successfully in the background without injecting stream receipt deltas into client responses.

@ranxianglei ranxianglei changed the title feat(compress): add streamMarkers setting to suppress streaming receipts (#3906) [PR] feat(compress): add streamMarkers setting to suppress streaming receipts (#3906) Oct 27, 2026
@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

查重结论:重复 —— 与 #1701(提案)/ #1708(PR)是同一需求:让压缩回执(📦/❌ 行)对客户端不可见、对模型保留。#1708 先到(2026-09-29),方案经 owner 拍板,实现与测试完整,现处待审/待合并;#4934 后到(2026-10-26)。按规则打 duplicate 标签,关闭由 owner 决定。

标签: duplicate, scope/wiring, p3(功能 PR,与 #1701/#1708 的回执投递模式工作重复;请求管道域;功能级影响)

对 #4934 的独立审核发现(非引用 #1708 结论)

逐文件读了 PR diff,并对 master 上每一个 marker 发射点做了代码核对:

  1. 主路径不生效。 PR 描述说要抑制"streaming receipts",但真正的流式回执发射点是 src/loop/core.ts:1213(runCompressLoop 里 yield adapter.emitMarker(...),即流入客户端流的 delta 字节)——PR 完全没碰这一处。LoopCtx.streamMarkers(src/loop/core.ts:222)声明后全仓无任何读取点,是死代码。实际生效的只有一处:非流式 Responses JSON 车道 src/compress-loop-responses.ts:133。对描述中点名的流式客户端(OpenCode/Pi/Cursor),设 streamMarkers: false 零效果。
  2. 环境变量不存在。 BILI_STREAM_MARKERS 全仓唯一出现位置是文档行 website/config-reference/compress.yaml:239;代码中没有任何 env 读取或 knobs 注册。PR 正文"Verified ... BILI_STREAM_MARKERS=0"不可能成立。同级字段 visibilityMarkers 也没有 env var;按项目 env 纪律(彻底整治环境变了滥用,除非必要都走配置文件 #2030),新增 env var 需要类别论证 + owner 事前批准。
  3. 零测试。 6 个改动文件里没有一个是测试文件;CI 的 docs-sync 红(fork PR 导致全部 test lane skip)。
  4. 缺 config surface 章节。 AGENTS.md 要求配置变更必须说明"现有面为何表达不了/考虑过哪些机制/迁移故事",PR 正文均无;标题还引用了无关的 Plugin lanes: host declares exposed bili tools per request via x-bili-plugin-exposed-tools (structural fix for #3884/#3600 name-guessing) | 插件车道:宿主按请求声明暴露的 bili 工具(根治 #3884/#3600 认名字脆弱性) #3906(那是 x-bili-plugin-exposed-tools header 问题)。
  5. 小瑕疵:src/server/relay.ts 两处(:2081/:2228)各多调一次 resolveCompress 只为取一个新字段,应复用同一次结果。

为什么不按外部 PR 规则直接重构补全

这个 PR 的问题不在代码质量,而在机制选择本身:#1708 的 config-surface 章节明确记录了 owner 拍板的决定——不给 compress. 新增兄弟字段*(visibilityMarkers 三态演进保持一个关注点一个旋钮)。把 #4934 修完就是同一关注点的第二套机制,与 #1708 正面冲突。所以正确处置是并入 #1708,不是修补。

已核实 #1708 头分支恰好补齐了 #4934 漏掉的点位:clientMarkers = visibilityMode === "stream" 门控 SSE emit 点(#1708 分支 src/loop/core.ts:1220),且额外带"终态失败向客户端透出恰好一条可见 ❌ 行"的设计——比 #4934 的语义更完整。

给作者的建议

等 #1708 合并后使用 compress.visibilityMarkers: "model-only":客户端流零回执字节(含流式)、模型侧回执保留、终态失败留一条可见行——完全覆盖你 PR 描述的需求。然后关闭 #4934(或由 owner 关)。

结构化八问

  1. 是什么问题:功能请求——压缩回执不想出现在客户端流里,但要留在模型上下文;现有 visibilityMarkers: false 会把两侧一起关掉,表达不了这个诉求。
  2. 什么原因导致的:不是缺陷,是配置面的缺口——一个布尔把"客户端可见性"与"模型侧注入"两个独立关注点绑在了一起。
  3. 影响范围与严重程度:功能级,不影响现有用户;但若按现状合并,设置 streamMarkers: false 的用户在流式客户端(主场景)上得不到任何效果,属于"有开关不生效"的坑。
  4. 怎么修复的:本 PR 不修——并入 [PR] feat: visibilityMarkers tri-state — model-only receipt delivery #1708 的三态方案(已实现、已测试、owner 已拍板)。
  5. 是否有回归问题:默认值(undefined≡true)与现状逐字节一致,无回归;风险在合并后遗留死接口字段 + 文档化的假 env var,成为后续维护债。
  6. 是否破坏缓存:不涉及(未触碰缓存/重试/去重键;marker 注入位置的缓存稳定性由 [PR] feat: visibilityMarkers tri-state — model-only receipt delivery #1708 的方案单独处理并测试)。
  7. 是否改了设计方向:试图为同一关注点引入第二个旋钮,与 Proposal: model-only delivery mode for visibility markers — proxy internal ACKs are not included in the client conversation history | proposal: visibility markers 的 model-only 投递模式——proxy 内部回执不进客户端对话历史 #1701/[PR] feat: visibilityMarkers tri-state — model-only receipt delivery #1708 已拍板方向(单旋钮三态)相悖——这正是它不该合入的原因。
  8. 是否引入了新的配置:是——compress.streamMarkers(+ 文档化但未实现的 BILI_STREAM_MARKERS)。两者均与 [PR] feat: visibilityMarkers tri-state — model-only receipt delivery #1708 方案冲突,不应进入配置面。

判定:不合入。 已标为 #1708/#1701 的重复,待 owner 关闭;需求本身由 #1708 合并后满足。

@ranxianglei ranxianglei added duplicate This issue or pull request already exists p3 scope/wiring labels Oct 27, 2026
ranxianglei pushed a commit to fathonix/billion-context that referenced this pull request Oct 27, 2026
… PR ranxianglei#4934

Align-refactor (review of ranxianglei#4935): this PR is scoped to the bare-announcement
terminal-turn retry (ranxianglei#3905 symptom), but it also carried the LoopCtx
streamMarkers field and the emitMarker consumption gate that belong to the
streamMarkers setting feature. That feature has its own PR (ranxianglei#4934, which
wires the config surface but lacks these two hunks) — keeping them here makes
ranxianglei#4934 unable to compile standalone and creates a merge-order dependency
between two independent features. The hunks move to ranxianglei#4934 so each PR is a
closed loop.
ci-check added 2 commits October 27, 2026 16:27
Align-refactor (review of ranxianglei#4935): this PR defines the streamMarkers field on
LoopCtx and wires the config surface end-to-end, but nothing ever reads the
field — the emission gate that honors it was shipped in PR ranxianglei#4935 (the
announcement-retry PR), which makes this setting a dead knob on its own and
couples the two PRs into a merge-order dependency. Move the consumption gate
(and its failure-mode comment) here from ranxianglei#4935 so each PR is a closed loop.
Behavior with the default (unset) is unchanged: markers still stream.
…rs (ranxianglei#2107)

Align-refactor (review of ranxianglei#4935): the PR's website/config-reference/compress.yaml
seed edit was committed without re-running tools/gen-config-docs.mjs, so the
ranxianglei#2107 docs-sync drift guard goes red on this head. Regenerate the four derived
artifacts (CONFIGURATION.md / CONFIGURATION.zh-CN.md / website/main.js /
website/docs/index.html) — content is exactly the new streamMarkers row plus
its BILI_STREAM_MARKERS env index entry.
@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

merge-guard r1 处理完成(PR #4938,head 分支 2026-10-27_zero-fold-calibrated-fit):

  • 同步:本轮唤醒时 origin/master(c499b1450)已被并发 worker 合入 head 分支——新 head 29e9cde5d,父提交为旧 head 654f84b62 + master tip c499b1450,无需重复推送。
  • 验证:合并提交的 tree 与对两个父提交重新执行 git merge-tree 的结果逐字节一致 → 零手动冲突解决、零设计决策;master 此后未再前进。
  • 当前状态:PR 不再 behind master;mergeable=true,mergeable_state=blocked(新 head 上 CI 运行中,gate/build-artifact 已绿)。
  • 已在 GitHub PR 上留一行结果评论(comment id 6439982336)。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

merge-guard r2 处理完成(PR #4938)——本轮为过期触发,无需任何操作:

  • 判定:fresh fetch 后按 ref 祖先关系验证,head 29e9cde5d(r1 同步产物)已包含 master tip c499b1450,GitHub base 同为 c499b1450 → PR 并不 behind。该通知应是基于 r1 同步推送前的旧状态发出的;不推送(推送只会是 no-op)。
  • CI 核验:head 上 55/55 check runs 全部 completed —— 39 success + 16 skipped(env-gated e2e 车道,常态)+ 0 failure。期间匿名 API 一度返回 unstable,重算后为陈旧缓存值;auth 侧当前 mergeable=true、mergeable_state=blocked = 等待人工 review 要求(检查项本身已全部满足),符合「合并仅人工」的既有纪律。
  • 已在 GitHub PR 留一行结果评论(comment id 6441151530)。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

merge-guard r3 处理完成(PR #4938)——又一次过期触发,无需任何操作:

  • 判定:fresh fetch 后 master tip 仍为 c499b1450(与 r2 完全未动),head 29e9cde5d 经 ref 祖先关系验证已包含它 → PR 并不 behind。该通知基于旧状态重复发出;不推送(推送只会是 no-op)。
  • 状态核验:auth API 返回 head 29e9cde5d / base c499b1450 / mergeable=true / mergeable_state=blocked,与 r2 逐字段一致(blocked = 等待人工 review,检查项本身 55/55 已全部绿,见 r2 记录)。
  • 已在 GitHub PR 留一行结果评论(comment id 6441259613),指向先前 r2 说明。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

merge-guard r4 处理完成(PR #4938)——第 4 次过期触发,无需任何操作:

  • 判定:fresh fetch 后 master tip 仍为 c499b1450、head 仍为 29e9cde5d(与 r3 完全未动),ref 祖先关系验证 head 已包含 master → PR 并不 behind。不推送(no-op)。
  • 状态核验:auth API 返回 head 29e9cde5d / base c499b1450 / mergeable=true / mergeable_state=blocked,与 r3 逐字段一致(blocked = 等待人工 review,检查项 55/55 已全部绿)。
  • 已在 GitHub PR 留一行结果评论(comment id 6441310544)。

提醒:同一静态 state 已连续 4 次触发 behind 通知,guard 的 behind 判定疑似基于旧快照而非实时祖先关系,建议运维侧核查触发逻辑。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

merge-guard r5 处理完成(PR #4938)——第 5 次过期触发,无需任何操作:

  • 判定:fresh fetch 后 master tip 仍为 c499b1450、head 仍为 29e9cde5d(与 r4 完全未动),ref 祖先关系验证 head 已包含 master → PR 并不 behind。不推送(no-op)。
  • 状态核验:auth API 返回 head 29e9cde5d / base c499b1450 / mergeable=true / mergeable_state=blocked,与 r4 逐字段一致(blocked = 等待人工 review,检查项 55/55 已全部绿)。
  • 已在 GitHub PR 留一行结果评论(comment id 6441375473)。

提醒:同一静态 state 已连续 5 次触发 behind 通知,guard 的 behind 判定疑似基于旧快照而非实时祖先关系,建议运维侧核查触发逻辑。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

merge-guard r6 处理完成(PR #4938)——第 6 次过期触发,无需任何操作:

  • 判定:fresh fetch 后 master tip 仍为 c499b1450、head 仍为 29e9cde5d(与 r5 完全未动),ref 祖先关系验证 head 已包含 master → PR 并不 behind。不推送(no-op)。
  • 状态核验:auth API 返回 head 29e9cde5d / base c499b1450 / mergeable=true / mergeable_state=blocked,与 r5 逐字段一致(blocked = 等待人工 review,检查项 55/55 已全部绿)。
  • 已在 GitHub PR 留一行结果评论(comment id 6441417264)。

提醒:同一静态 state 已连续 6 次触发 behind 通知,guard 的 behind 判定疑似基于旧快照而非实时祖先关系,建议运维侧核查触发逻辑。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

merge-guard r7 处理完成(PR #4938)——第 7 次过期触发,无需任何操作:

  • 判定:fresh fetch 后 master tip 仍为 c499b1450、head 仍为 29e9cde5d(与 r6 完全未动),ref 祖先关系验证 head 已包含 master → PR 并不 behind。不推送(no-op)。
  • 状态核验:auth API 返回 head 29e9cde5d / base c499b1450 / mergeable=true / mergeable_state=blocked,与 r6 逐字段一致(blocked = 等待人工 review,检查项 55/55 已全部绿)。
  • 已在 GitHub PR 留一行结果评论(comment id 6441506992)。

提醒:同一静态 state 已连续 7 次触发 behind 通知,guard 的 behind 判定疑似基于旧快照而非实时祖先关系,建议运维侧核查触发逻辑。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

merge-guard r8 处理完成(PR #4938)——第 8 次过期触发,无需任何操作:

  • 判定:fresh fetch 后 master tip 仍为 c499b1450、head 仍为 29e9cde5d(与 r7 完全未动),ref 祖先关系验证 head 已包含 master → PR 并不 behind。不推送(no-op)。
  • 状态核验:auth API 返回 head 29e9cde5d / base c499b1450 / mergeable=true / mergeable_state=blocked,与 r7 逐字段一致(blocked = 等待人工 review,检查项 55/55 已全部绿)。
  • 已在 GitHub PR 留一行结果评论(comment id 6441578348)。

提醒:同一静态 state 已连续 8 次触发 behind 通知,guard 的 behind 判定疑似基于旧快照而非实时祖先关系,建议运维侧核查触发逻辑。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

merge-guard r9 处理完成(PR #4938)——第 9 次过期触发,无需任何操作:

  • 判定:fresh fetch 后 master tip 仍为 c499b1450、head 仍为 29e9cde5d(与 r8 完全未动),ref 祖先关系验证 head 已包含 master → PR 并不 behind。不推送(no-op)。
  • 状态核验:auth API 返回 head 29e9cde5d / base c499b1450 / mergeable=true / mergeable_state=blocked,与 r8 逐字段一致(blocked = 等待人工 review,检查项 55/55 已全部绿)。
  • 已在 GitHub PR 留一行结果评论(comment id 6441664918)。

提醒:同一静态 state 已连续 9 次触发 behind 通知,guard 的 behind 判定疑似基于旧快照而非实时祖先关系,建议运维侧核查触发逻辑。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

merge-guard r11 处理完成(PR #4938)——第 11 次过期触发,无需任何操作:

  • 判定:fresh fetch 后 master tip 仍为 c499b1450、head 仍为 29e9cde5d(与 r10 完全未动),ref 祖先关系验证 head 已包含 master → PR 并不 behind。不推送(no-op)。
  • 状态核验:auth API 本轮恢复正常,返回 head 29e9cde5d / base c499b1450 / mergeable=true / mergeable_state=blocked,与 r10 之前各轮逐字段一致(blocked = 等待人工 review,检查项 55/55 已全部绿)。
  • 已在 GitHub PR 留一行结果评论(comment id 6442221177)。

提醒:同一静态 state 已连续 11 次触发 behind 通知,guard 的 behind 判定疑似基于旧快照而非实时祖先关系,建议运维侧核查触发逻辑。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

merge-guard r12 处理完成(PR #4938)——第 12 次过期触发,无需任何操作:master tip c499b1450、head 29e9cde5d 与 r11(约 6 分钟前)完全未动,ref 祖先关系验证 head 已包含 master → 不 behind,不推送;auth API 核验 mergeable=true / mergeable_state=blocked,各字段与历轮一致。结果评论 id 6442330926。同一静态 state 已连续 12 次触发,guard 的 behind 判定疑似基于旧快照而非实时祖先关系,建议运维侧核查触发逻辑。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

merge-guard r13 处理完成(PR #4938)——第 13 次过期触发,无需任何操作:master tip c499b1450、head 29e9cde5d 与 r12(约 3 分钟前)完全未动,ref 祖先关系验证 head 已包含 master → 不 behind,不推送;auth API 核验 mergeable=true / mergeable_state=blocked,各字段与历轮一致。结果评论 id 6442393554。同一静态 state 已连续 13 次触发,guard 的 behind 判定疑似基于旧快照而非实时祖先关系,建议运维侧核查触发逻辑。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

Merge-guard 处理完成(PR #4938,head 分支 2026-10-27_zero-fold-calibrated-fit):

  • 无需 push:「behind」信号是过期的——head 29e9cde5d 已包含当前 origin/master(c499b1450,fresh fetch 后用 git merge-base --is-ancestor 验证为祖先),同步发生在 10:40 UTC(约 2 小时前)。
  • API 核实状态:open、mergeable=true、head 上 55 个 check runs 全部 success/skipped、mergeable_state=blocked(等 review,非冲突)。
  • 无设计冲突,未开 decision-request issue;已在 PR 留一行结果评论。

备注:guard 消息里的标题("streamMarkers setting")与实际 PR #4938 标题不符,按 PR 编号为准处理。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

Merge-guard 二次触发(重复 "behind" 信号):fresh fetch 后重新验证,PR #4938 head 29e9cde5d 仍包含当前 origin/master(c499b1450),无需 push。状态:open / mergeable=true / blocked(等 review,非冲突)。已在 PR 留一行复核评论。另注意:guard 消息标题("streamMarkers setting")与 PR 实际标题不符,已一并标注给 guard 管道排查。

@ranxianglei

Copy link
Copy Markdown
Owner

(ai: vllm-qwen/qwen3.8-27b)

Merge-guard sync: merged origin/master (c499b1450) into head — clean, no conflicts; new head ba387a7f8. State after push: open, mergeable=true, mergeable_state=blocked (checks running / awaiting review; no longer "behind"). Note: the guard fired this under PR number #4938, but its title matches this PR (#4934) — flagging the number mismatch to the guard pipeline.

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

Merge-guard 第三次触发,这次查清了根因:guard 的 PR 编号错了。消息里的标题("feat(compress): add streamMarkers setting…(#3906)")实际对应 PR #4934(外部贡献者 fathonix 的 fork 分支),而不是 #4938。#4938(zero-fold calibrated fit)本身不 behind、无需动。

已对真正的目标 PR #4934 执行同步:

待 owner 路由:merge-guard 管道的编号映射 bug(标题与编号错位 4 位,连续三次触发都带错号)不属于 billion-context 仓库代码,未在该仓立项;请指示在哪个项目跟进。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

说明:上面这条是我在 PR #4934(streamMarkers 同步结果)上发的评论,被上游同步管道镜像到了 #4938 线程——还是那个编号错配问题,连评论镜像都串号了。无需处理;#4934 的 behind 已消除,#4938 本身不 behind。guard 编号映射的修复等您路由到对应项目。

@ranxianglei

Copy link
Copy Markdown
Owner

(ai: vllm-qwen/qwen3.8-27b)

Merge-guard sync: merged origin/master (7f2e11904) into head — clean, no conflicts; new head 9b80de23e. State after push: open, mergeable=true, mergeable_state=blocked (checks/review pending; no longer "behind").

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

Merge-guard 第四次触发,这次是真 behind:master 前进到 7f2e11904(#4969/#4970/#4972 等合入),两个 PR 都落后了。已同步:

运维备注:① 共享 git clone 里发现一个损坏的本地 ref(wt-4974-ework-daemon,指向缺失对象)导致 fetch 失败,已删除该坏 ref 修复(无内容损失);② GitHub core API 限流 5000/5000 耗尽,等窗口重置后才完成 API 核验。结果评论已分别留在两个 PR。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b)

又是同一条镜像串号:这是我在 PR #4934 上发的同步结果评论,被上游同步管道再次镜像进 #4938 线程(同前一条说明,编号映射问题连评论镜像都受影响)。无需处理。

ranxianglei pushed a commit to Louie0806/billion-context that referenced this pull request Nov 14, 2026
… PR ranxianglei#4934

Align-refactor (review of ranxianglei#4935): this PR is scoped to the bare-announcement
terminal-turn retry (ranxianglei#3905 symptom), but it also carried the LoopCtx
streamMarkers field and the emitMarker consumption gate that belong to the
streamMarkers setting feature. That feature has its own PR (ranxianglei#4934, which
wires the config surface but lacks these two hunks) — keeping them here makes
between two independent features. The hunks move to ranxianglei#4934 so each PR is a
closed loop.

(cherry picked from commit fa60f8f)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

duplicate This issue or pull request already exists p3 scope/wiring

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants