Skip to content

[PR] docs: document DSH inspector fetch-accessor conflict + BILI_RECLAIM_FETCH_PATCH=0 workaround (#3528) - #3690

Merged
ranxianglei merged 1 commit into
masterfrom
2026-10-17_dsh-inspector-fetch-docs
Oct 18, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-10-17_dsh-inspector-fetch-docs

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Related to #3528.

Minimal docs-only stopgap (per the 止血例外 — a small mitigation PR preceding the complete root-cause fix): document the known incompatibility between native mode's default guarded-accessor globalThis.fetch and third-party components that require a plain writable data property — they read the property descriptor, find no value, and abort their fetch observer at load. Reported case: DSH Desktop's Developer Tools / NodeJS diagnostic plugin (@deepseek-ai/dsh-experimental-inspector).

Adds a coexistence note to the existing BILI_RECLAIM_FETCH_PATCH entry in both CONFIGURATION.md and CONFIGURATION.zh-CN.md: setting 0 (+ full host restart) falls back to the classic direct install so such observers load; the trade-offs (loss of self-heal re-arm + egress caveats) are already documented in the same entry.

No behavior / config-schema / wire / persistence / kernel change — prose only, zh+en mirrored. The root-cause fix (convert the guard to a writable data property, adopting third-party installs via #2804's integrity watchdog) is tracked separately on #3528 and will supersede this note once it lands.

@ranxianglei ranxianglei changed the title docs: document DSH inspector fetch-accessor conflict + BILI_RECLAIM_FETCH_PATCH=0 workaround (#3528) [PR] docs: document DSH inspector fetch-accessor conflict + BILI_RECLAIM_FETCH_PATCH=0 workaround (#3528) Oct 18, 2026
@github-actions

github-actions Bot commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-17_dsh-inspector-fetch-docs (d9a2610)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.4356-pr.3690.8dd42b2

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr3690.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

查重: 不重复。 检索了 open+closed issue/PR,无其他条目覆盖「为 #3528 的 fetch-accessor 冲突补文档绕行」。本 PR 与 #3528 是止血例外下的合法拆分:#3528 跟踪代码根治(data property + #2804 watchdog),本 PR 只把已实测验证的绕行写进文档——交付物不同(代码修复 vs 文档),且「最小缓解先行、根治收尾」正是政策允许的形态。

标签: dsh / scope/docs / p3——纯文档变更(不打 bug),针对 DSH 桌面 inspector 场景的已知冲突说明,无行为影响。

核对结论(分支 2026-10-17_dsh-inspector-fetch-docs @ c560e4e,对代码逐项验证):

  • diff 与描述完全一致:仅 CONFIGURATION.md 与 CONFIGURATION.zh-CN.md 各改 1 行——在既有 BILI_RECLAIM_FETCH_PATCH 条目追加共存提示,中英镜像,无其他文件、无空白噪音。
  • 事实核对(对 src/agent/fetch-chain/index.ts):默认路径确为 guarded accessor(L172-214,描述符只有 get/set、无 value 键);BILI_RECLAIM_FETCH_PATCH=0 时走 else 分支经典直装 globalThis.fetch = top(L215-219,普通可写数据属性,"value" in desc === true)——inspector 的守卫(!("value" in descriptor) 即抛错)随之通过。env 在进程加载期读一次、链每进程只装一次,所以「设 0 后完全重启宿主」的表述准确。
  • 代价引用正确:提示里「trade-offs above」指向同一行内既有的两段说明(失去自愈重武装→第三方重装后 bili 看不到模型流量;出口回退需在 bili 层配 proxy),均真实存在,未新造说法。
  • CI:静态门禁全绿(docs-sync / config-surface-guard / kernel-guard / version-guard / gate / lock-sync 等 11 项 success);e2e 各 lane 按 docs-only 预期 skipped;test lane 仍在跑(多数 queued,ubuntu-22 shard 3 in_progress)。mergeable=true,当前 blocked 只因 test 未出结果。

八问:

  1. 是什么问题:bili 原生模式默认把 globalThis.fetch 装成 get/set accessor,要求数据属性形态的第三方 fetch 观察者(DSH 桌面 experimental-inspector)加载即被拒;受影响的 DSH 用户此前没有任何官方文档化的绕行入口。
  2. 什么原因导致:accessor 载体形状(方式一安装的dsh 原生插件:llm-pi-ai 传输(OpenAI SDK + options.fetch 注入)绕过 globalThis.fetch 拦截,模型请求不进代理、压缩完全不生效 #1158/fix: guard native fetch intercept against third-party re-arm (#1158 L1) #1187 引入)按 JS 语言保证永远没有 value 键,与描述符型观察者的安全守卫互斥;根治(data property + [PR] fix(#2791): heal setter-invisible globalThis.fetch evictions in the native intercept chain #2804 watchdog)卡在 [PR] fix(#2791): heal setter-invisible globalThis.fetch evictions in the native intercept chain #2804 尚未合入,见 [plugin] Guarded globalThis.fetch accessor blocks coexisting fetch observers (dsh experimental-inspector fails to load) #3528。
  3. 影响范围与严重程度:所有启用 bili native 且挂了描述符型 fetch 观察者的宿主——已报告 DSH 桌面 0.2.1-rc.x + bili 0.1.197/0.1.199,三环境复现,且 DSH 官方 profile 把 captureFetch 钉死为 true,属必现而非边缘场景;该第三方插件完全无法启动,bili 本体与其他流量不受影响。本 PR 自身零行为变更。
  4. 怎么修复的:纯文档止血——把已在三环境实测验证的绕行(env 设 0 + 完全重启宿主,且不丢 Host 侧抓包)及其代价写进配置参考中英两版,让受影响用户有据可依;[plugin] Guarded globalThis.fetch accessor blocks coexisting fetch observers (dsh experimental-inspector fails to load) #3528 根治 PR 落地后此段说明会被 supersede。
  5. 是否有回归问题:不涉及——无行为/配置面/wire/持久化/kernel 变更;CI 的 config-surface-guard 与 docs-sync 门禁通过佐证配置面与中英同步未被破坏。
  6. 是否破坏缓存:不涉及(host 侧拦截链文档,不碰任何失效策略)。
  7. 是否改了设计方向:不涉及。
  8. 是否引入了新的配置:无新 key、无新默认值——只是给既有 BILI_RECLAIM_FETCH_PATCH 条目补充一条共存说明。

判定:文档与代码事实一致、diff 干净、静态门禁已过,待 test lane 出绿即可合并;test 结果出来后我会回帖确认。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

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

CI 终态与红腿归因(承接首条审核回复):

八问:

  1. 是什么问题:为 [plugin] Guarded globalThis.fetch accessor blocks coexisting fetch observers (dsh experimental-inspector fails to load) #3528(fetch-accessor 挡住 DSH inspector 加载)补一条文档化的绕行说明——BILI_RECLAIM_FETCH_PATCH=0 + 完全重启宿主。
  2. 什么原因导致:accessor 载体形状无 value 键,描述符型观察者拒载;根治卡在 [PR] fix(#2791): heal setter-invisible globalThis.fetch evictions in the native intercept chain #2804 未合入([plugin] Guarded globalThis.fetch accessor blocks coexisting fetch observers (dsh experimental-inspector fails to load) #3528 跟踪)。
  3. 影响范围与严重程度:文档覆盖所有 bili native + 描述符型 fetch 观察者的宿主(已报告 DSH 桌面,三环境复现、profile 钉死 captureFetch=true 属必现);本 PR 自身零行为变更。
  4. 怎么修复的:纯文档止血,中英镜像写入既有配置条目;根治 PR 落地后此段 supersede。
  5. 是否有回归问题:无产品回归——零行为/配置面/wire/持久化/kernel 变更(config-surface-guard、docs-sync 门禁佐证)。唯一 CI 红腿经上述证据链归因为 The plugin-bypass test intermittently hangs on Windows CI, turning the entire test shard red. | plugin-bypass 测试在 Windows CI 偶发挂死,拖红整个测试分片 #3702 环境类问题,非本 PR 引入。
  6. 是否破坏缓存:不涉及。
  7. 是否改了设计方向:不涉及。
  8. 是否引入了新的配置:无新 key/默认值,仅给既有条目补说明。

判定与建议:PR 内容本身可合并——diff 已逐项对代码验证、门禁全过、唯一红腿是已立项跟踪的 CI 环境问题且机制上与 2 行 markdown 无关。给你两个选项,我推荐前者:

按规矩我不代合并——你点头后自行合并即可(或告诉我等 #3702,我就把状态挂起)。

@ranxianglei
ranxianglei merged commit 6f2b113 into master Oct 18, 2026
110 of 146 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.577-master.6f2b113 (rolling master tag).

npm install -g billion-context@0.0.577-master.6f2b113  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant