Repository navigation
[PR] fix: Misc lane minor fixes, Part 4 — hermes plain-http proxy routing + acp_status occupancy anchor | fix: 其他车道小修合集第四辑 —— hermes plain-http 代理路由 + acp_status 占用锚点 - #5987
Conversation
… lifetime "original" total as current context (#5021) acp_status gave an absolute `BILLED INPUT … tok` with no denominator, and the kernel's `COMPRESSED BLOCKS — N active (X summary, Y original)` header prints a LIFETIME reclaimed total one line above it. An agent that cannot see the route's window has no anchor, so both figures read as current occupancy. Measured incident: a session at 116,902 of a 1,000,000-token window (11.7%, peak 16.9%) reported "the context is exhausted" to its user and stopped mid-task, citing the 1,214.1K lifetime original and the 4.3K remaining foldable mass as its evidence. The report now always carries the missing denominator when a billed sample exists: CONTEXT: 116902 / 800000 tok used (14.6%) · 683098 tok remaining of the input budget Guarded: no billed anchor or a non-positive limit prints no line, and remaining clamps at 0 so an over-limit reading never shows a negative budget.
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.8718-pr.5987.a2454f9This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr5987.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 查重: 不重复。 已列出全部 open [PR] 行逐一比对:没有第二个 PR 指向 #5116(hermes plain-http 路由)或 #5021(acp_status 占用锚点);本 PR 是这两个已评审小修的唯一送审载体(cherry-pick 标签: bug + hermes + scope/kernel + p2(理由:两处均为缺陷修复;涉及 hermes 车道与上下文管理面;plain-http hermes provider 在特定条件下完全收不到压缩,属"能用但有明显问题/需绕行"档,故 p2)。 独立审核进行中(方向关 → 回归清点 → 代码 → 测试有效性 → diff 整洁度),跑完定向测试与 CI 状态核对后按八问体例给结论。 |
…hips it (#5116) Review fix on this branch: the plugin-lane sentence claimed HTTP_PROXY / NO_PROXY routing that this PR does not ship for the native plugin. The plugin's apply_env still sets only the HTTPS pair + CA bundles; the plain-http half lives in open PR #5117 (adds the HTTP pair + NO_PROXY setdefault to apply_env). Reword so each claim matches code on master: the launcher lane (this PR) routes both schemes; the plugin lane gets them via #5117.
[bot] 🏷 审核完成:可合入(新 head c135d08 CI 全绿)。审核中发现一处文档超前于代码的表述,已直接修掉(详见下)。 审核中顺手修(新增 commit c135d08,已推本 PR 分支)docs/clients.md 的 Hermes 段原称原生插件车道也做 结构化八问1. 是什么问题:两个独立小修合并送审——① hermes 启动器只设 2. 什么原因导致的:① hermes 的 httpx 按协议解析代理环境变量, 3. 影响范围与严重程度:① 4. 怎么修复的:① hermes spawn 路径补 5. 是否有回归问题:逐项清点既有行为——
6. 是否破坏缓存:不涉及。不触碰缓存/重试/增量游标/去重键;CONTEXT 行只是工具输出文本的一行增量。 7. 是否改了设计方向:无转向。① hermes 车道对齐全舰队"env 路由 + 回环直连"惯例(i18n note 自 9/27 起就承诺 "http absolute-form forwarding",本次让现实匹配已文档化的契约);② acp_status 增加观测锚点,不改压缩决策管线。已知残留:#5021 验收项 2(kernel 报告头 COMPRESSED BLOCKS … original 累计量加"已回收、不计入当前请求"标注)属 kernel 变更(human-gated),外部作者明确未纳入本 PR——建议 owner 决定是否另立 kernel follow-up。 8. 是否引入了新的配置:无。无新 env/config/knob;NO_PROXY 常量是既有的 验证证据
协调备注(供 owner 参考,我不动手)
结论:可合入。 两个修复各自闭环,CI 在 pushed head 上全绿,唯一文档漂移已当场修复。 |
两个已评审小修合并送审(一 PR 一合)
HTTPS_PROXY(https)+HTTP_PROXY(plain-http)+NO_PROXY回环直连),此前只有 HTTPS_PROXY,plain-http provider 对 bili 不可见贡献者身份保留
#5023 用 cherry-pick 原提交
898954f8合入,git author 保留为Augenblick0v0 <caiyanhong35@gmail.com>;squash 合并后作者身份仍在合并历史里。冲突处理(合入 master ec4b9f7 时)
CLIENTS.md/CONFIGURATION.md现在只是重定向 stub → 内容改写重投到docs/clients.md+docs/configuration.md(表格行 + file-free 段 + README 启动器表 hermes 行)。代码部分(src/launcher.ts+tests/launcher.test.ts)3-way 合并干净。预检(本地,2026-11-10)
npm run buildOK,tsc --noEmit0 错Closes #5116
Closes #5021