Repository navigation
[PR] docs: document DSH inspector fetch-accessor conflict + BILI_RECLAIM_FETCH_PATCH=0 workaround (#3528) - #3690
Conversation
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.4356-pr.3690.8dd42b2This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr3690.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(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 场景的已知冲突说明,无行为影响。 核对结论(分支
八问:
判定:文档与代码事实一致、diff 干净、静态门禁已过,待 test lane 出绿即可合并;test 结果出来后我会回帖确认。 |
c560e4e to
d9a2610
Compare
(ai: vllm-qwen/qwen3.8-27b) CI 终态与红腿归因(承接首条审核回复):
八问:
判定与建议:PR 内容本身可合并——diff 已逐项对代码验证、门禁全过、唯一红腿是已立项跟踪的 CI 环境问题且机制上与 2 行 markdown 无关。给你两个选项,我推荐前者:
按规矩我不代合并——你点头后自行合并即可(或告诉我等 #3702,我就把状态挂起)。 |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.577-master.6f2b113 # this exact build
npm install -g billion-context@master # always the newest merged build
|
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.fetchand third-party components that require a plain writable data property — they read the property descriptor, find novalue, 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_PATCHentry in bothCONFIGURATION.mdandCONFIGURATION.zh-CN.md: setting0(+ 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.