Repository navigation
[PR] docs(codex): Codex Desktop Composer predictions — custom-provider threads are ineligible (#3408) - #3409
Conversation
…-provider threads (#3408)
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.4006-pr.3409.52009b8This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr3409.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) 查重:不重复。 已检索 open/closed issue 与近期 PR——#3408 本身就是本 PR 要关闭的源 issue(文档请求),仓库内无其他针对「Codex Desktop Composer 预测资格」的在途工作;相关但不同的 #3176/#3178(一键安装)作者已在 PR 描述里说明为何不并入本文档,判定成立。 审核结论(独立审过,非转述 issue)按 PR review 规范逐项核过,不是照抄 issue 分析: ① 方向关:issue #3408 的三项诉求(记录客户端门槛、澄清受支持的路由姿态、无解时明说)与 PR 内容一一对应,方向正确。 ② 事实核对(我逐条对过代码,不是只读 diff):
③ 回归审查:纯插入 2 文件 20 行,现有段落零改动,不触碰任何代码/配置/wire 路径——既有行为清单为空,无回归面。 ⑤ diff 整洁度:干净,每一行都服务于本 PR 目的;无关改动/空行重排:无。 CI:全部 gate 绿(static-gates、kernel-guard、docs-coverage、lock-sync、lane-guard、test-import-graph 等);real-client lanes 正确 skipped(未触碰其触发路径);test 分片 3/6 绿,剩 3 个(in_progress)——docs-only 变更,预计全绿,跑完我再补一句确认。 Rebase:master 领先 27 个提交,无一触碰这两个文件;试验性 rebase 干净(未推分支,BEHIND 不构成阻塞,GitHub 侧 mergeable=true)。 结构化八问
判定:可合并(待剩余 3 个 test 分片全绿后补最终确认;docs-only,风险面为零)。 |
(ai: vllm-qwen/qwen3.8-27b) CI 跟进(接上一条评论的审核结论;八问结论维持不变,只补充 Q5 回归项的最终判定与处置): 红的原因——不是本 PR 的回归。 处置(几行级小修纪律:修复 PR + 记录 issue 各一):
当前 CI:已对失败 job 触发 rerun-failed-jobs;其余 17 个 job 全部 success,仅 判定维持:可合并(docs-only、零行为面)。若 rerun 再次变红,继续排查并在本线程报告。 |
…t fixed sleep) Discovered while reviewing PR ranxianglei#3409: its windows-latest(22,1) shard failed on 'retired stall guard: mid-stream silence survives any short window' (first chunk should have flowed through) — a fixed 2s wall-clock sleep that starves under runner load. Convert both fixed-sleep waits in this file that gate assertions on async events to the file's own deadline-poll idiom; the mid-stream test keeps its 2s observation floor so the negative assertions still cover a window far past the retired 400ms guard.
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.665-master.b2cbfcf # this exact build
npm install -g billion-context@master # always the newest merged build
|
Closes #3408
What
Adds one Codex subsection to
CLIENTS.md(mirrored inCLIENTS.zh-CN.md) documenting the client-side Composer-prediction eligibility gate observed on Codex Desktop 26.1013.3656.0:openaiprovider; any other provider selectsunsupported_providerand the client returns before generating a prediction. This happens entirely client-side, before any model request could reach billion-context — so missing predictions on custom-provider routes are expected client behavior, not a bili forwarding defect.HTTPS_PROXY+SSL_CERT_FILE, what thebili codexlauncher injects) intercepts below the provider layer, so the thread keeps its built-inopenaiidentity + ChatGPT auth — mechanically the only posture that can keep eligibility intact. The doc states this is runtime-unverified on a Desktop build (no matched A/B yet) and invites confirmation reports back to Codex Desktop Composer predictions: document custom-provider eligibility limitation and supported routing options #3408.openaior patching the client check is unsupported and not documented as a workaround.Scope & verification
src/,tests/or docs (consistent with the reporter's review of master73d9360c).model_providersentry sits on the ineligible side") already covers that work when it lands.