Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ Versions follow the merge of a `*_release-v*` branch; CI publishes to npm on tag
## [Unreleased]

### Fixed
- **磁盘写入临时失败后,会话不再陷入「之后每次触碰都硬报错」(#4788 phase-2 副作用)**:phase 2 的闲时内存折叠会在一次成功保存之后,把内存里的原始内容降成「用时从磁盘重新加载」的惰性代理。若此时盘上信封恰好写不进/已损坏(瞬时写入失败或损坏),下一回合采纳内核新内容时要先读旧内容做差集——按 #2674 纪律它会抛「无法重新物化、拒绝瘦身视图」——整个采纳直接炸掉:新引用记不进去,会话从此每次访问都报 `[persist] resident content store … could not be re-materialized`,直到人工修好文件。现在旧内容重加载失败(镜像与 sidecar 双双已不可读)时按「无存活旧引用」处理——旧字节那时本已不可恢复——新库照样完整采纳、标脏并在下次保存落盘,会话随瞬时故障消除而恢复而不是持续报错。tests/store.test.ts 的 flushAll 瞬时失败重试回归恢复绿。
- **重复调用守卫不再一口咬死合法等待/轮询(#5225)**:此前同一工具、同样参数连发到第 5 次时,守卫在调用执行前就掐掉整个回合——调试器等待(`kd_wait` 10 秒一次)、omp 任务轮询这类「参数本来就不变、结果随外部状态变化」的合法调用被整段杀掉(Pi Codemode、omp 两起真实报告,等待还没到期)。现在升级为三段式:连续第 3、4 次照旧随结果附警告;第 5 次改为只拒绝这一次调用并发出明确的最后警告(回合保留——模型此时把多次短等待合并成一次更长等待、或换参数换工具,计数立即重置);被拒之后仍一字不差地重发同样调用,才终止整个回合。真死循环保护不受削弱(最多多烧一次调用)。同时修正提示文案里两处误导说法(「字节级相同」实为规范化后相同;「同样的调用不可能有新结果」对轮询类工具不成立)。tests/tool-guardrails-pi.test.ts 更新升级链断言并新增合法轮询逃生回归。
- **两份安装(全局树 + 宿主自带副本)差一个自动更新版本时不再互相卡死、流量裸奔(#4125)**:机器上 bili 本来就有两份合法安装——npm 全局树和宿主管理器自带的独立副本,各由各的更新节奏往前走。当全局树领先一个版本时:宿主插件想接上已占端口的旧进程 →「代码指纹不一致」拒绝采纳(#1225);旧进程置换只敢碰更老的邻居,而占位者是更新的那份,永远够不着(#3544);新拉起的子进程一绑定端口就撞口、向这个谁也不敢采纳的持有者让位退出——三条路全堵死,整条车道直接连模型(无压缩),直到有人整机重启对齐版本。修复三面一起落:①拉起子进程时把自己的代码摘要随环境传下去(`BILI_SPAWN_FINGERPRINT`,64 位 hex sha256;非法/缺失回落本地重算,沿用 #1225「陌生进程自称身份不采信」原则)——「同一构建」从此比字节不比口号;②宿主侧:候选者因指纹不一致被拒之前,先问一次**活着的**持有者真实版本号——严格更新、同车道、同形状、健康应答为证 → 采纳骑上而不是拒掉(跨车道和用户自己起的实例仍一律不碰,它们没有 bili 替身可退路);③子进程侧:确认端口被「严格更新的同车道同形状存活实例」占住时不再逐级换口(那只会造出第二个没人路由到的影子实例),改走既有的采纳信号退出(exit 3),由宿主骑上更新版。手动启动与升级替换流程语义完全不变。`tests/issue4125-two-install-deadlock.test.ts`(9 例)+ listen-policy/issue3654 判定表扩展钉住全部三面。
- **压缩「总是失败、要重试很多次才成功」的活锁(#4521)**:长会话里模型重报已被折叠覆盖的区间、或把 endId 猜到尚未发号的 ref 之上、或整段落在保护区,这些「其实无事可做」的请求一律被判 FAILED——原子批整体拒绝、断路器计数、模型照失败提示再猜再试,形成「失败→重试→再失败」循环(实测会话 01a18a4d 在 20:09 连续 4 次 FAILED 才成功)。现在五处修正:①endId 越界自动钳到最高已发 ref(警告提示,不整批拒);②区间全覆盖既有活动块=幂等 no-op 成功收据(`noop: true`,提示用 bN..bM 改写而非重发原文),不失败、不进断路器;③纯保护区区间同样 no-op(警告明说勿重发);④保护区 fatal 不再中止整批,只降级该区间;⑤新增 armed-but-silent 状态行:tier 级 nudge 已备好但本轮不投横幅时(退避/节拍/模型定时),以临时 user 消息刷新「最高已发 ref + 当前可压区间」,模型不再凭记忆猜号;全新会话的低于阈值计划保持完全静默(#196 域隔离、#3910 基线不破坏)。
- **自动升级换代旋转的「假存活」误判(#5167)**:旧实例接受 `/__bili/shutdown` 后毫秒级就关 listener(口已释放),但存量 keep-alive 连接照常应答——这是排水的本意(#3890 后最坏 (1+10)×10s 才退进程)。而两条旋转等待(launcher `rotateStalePredecessor` 每 200ms `fetchHealthInfo`、dsh `rotatePinnedStaleProxy` 每 500ms `fetchProxyVersion`)都用全局 fetch 的连接池轮询,轮询节拍远小于服务端 5s keepAliveTimeout,永远落在预热过的池化 socket 上 → 把「正在排水」误判为「没退出」,12s 预算耗尽得到假阴性:dsh 宿主 attach-anyway 骑上将被强退的旧实例、launcher 回退 spawn 阶梯,新旧两进程同写一份 machine-global 会话存储(index.db 双写横幅、#5046 SQLITE_BUSY、JSON 状态互踩)。修复:旋转等待的全部请求(含 shutdown POST)改带 `Connection: close` 每轮全新连接,「应答」重新等于「listener 还在收新连接」=真正的口释放信号;同步修正 12s 预算的过时注释(它只需覆盖 shutdown 请求被处理的延迟,不需覆盖进程退出)。`tests/issue5167-drain-aware-rotation.test.ts` 用真实排水 http 服务器(无 fetch mock、单连接 dispatcher 钉住池化拓扑)双向钉住:排水中的 resident 必须判为已释放,真占口不退的 holder 仍走超时回退。
Expand Down
4 changes: 2 additions & 2 deletions CONFIGURATION.md
Original file line number Diff line number Diff line change
Expand Up @@ -181,7 +181,7 @@ This index is generated from `website/config-reference/*.yaml` — edit the seed
| `guardrails` | object | {} (all defaults) | — | Guardrails: tool-output guardrails for the pi/omp plugin bundles (#3066) plus the proxy-side text-run stream guard (#3406). |
| `guardrails.bashTimeout` | number | 60 | BILI_GUARDRAIL_BASH_TIMEOUT | Seconds injected as the bash tool's timeout when the model omits it (#3066 owner intent, re-affirmed #3366: an unsupervised bash call could hang a pi session for a whole day — the host schema provides no default). Set N to tune, 0 to disable injection (pi-native no-default). |
| `guardrails.maxOutputBytes` | number | 50000 | BILI_GUARDRAIL_MAX_OUTPUT_BYTES | Combined text-output byte cap per tool result in the pi/omp plugin (0 disables the cap). Over-cap output is truncated head-first with a notice pointing at the host-saved full output. |
| `guardrails.repetition` | boolean | true | BILI_GUARDRAIL_REPETITION | Identical-call loop-breaker for the pi/omp plugin (warn at 3, abort at 5 consecutive byte-identical calls). false / env 0 disables it. |
| `guardrails.repetition` | boolean | true | BILI_GUARDRAIL_REPETITION | Identical-call loop-breaker for the pi/omp plugin: warns from the 3rd consecutive identical call, issues ONE final refusal (that call is refused but the turn stays alive) at the 5th so a legitimate wait/poll can still switch to a longer wait, and aborts the turn only if the identical call is repeated again after that refusal (#5225). false / env 0 disables it. |
| `guardrails.textRunThreshold` | number | 200 | BILI_GUARDRAIL_TEXT_RUN_THRESHOLD | Single-codepoint repetition breaker over decoded model text on the response stream (#3260; kill switch added by #3406 item 1 after the #3331 review). Trips at N consecutive identical codepoints - legit prose/code stays far below the 200 default, a symbol-loop model does not. Set N to tune, 0 (or negative) to disable: legit long same-char output (code comment separators, ASCII rules) is then never cut mid-stream. The thinking/reasoning channels sit inside this lane too. |
| `persist` | object | {} (all defaults) | — | Session persistence to disk under the XDG state dir. |
| `persist.enabled` | boolean | true | BILI_PERSIST | Master switch for writing session records to disk (0/false turns it off). |
Expand Down Expand Up @@ -275,7 +275,7 @@ This index is generated from `website/config-reference/*.yaml` — edit the seed
| `compress.maxSummaryLength` | number | kernel 20000 | — | Hard character cap on ONE generated summary; longer replies are rejected whole (no truncation, no retry). External summarizers are told this exact cap up front (#3635). 0 = unbounded. |
| `compress.minSummaryLength` | number | kernel 50 | — | Character floor for generated summaries; shorter replies are rejected whole. 0 = disabled. External summarizers are held to the same floor (#3635). |
| `compress.reconcile` | "off" \| "warn" \| "repair" | "repair" | BILI_FOLD_RECONCILE | Reconcile folded state when the client rewinds or rewrites history between turns. |
| `compress.promptPack` | string (builtin: "default", "lean", "chat") | builtin "default" | — | Compression prompt pack, resolved project pack → user pack → shipped pack → builtin; not gated by acknowledgePromptsRisk. |
| `compress.promptPack` | string (builtin: "default", "lean") | builtin "default" | — | Compression prompt pack, resolved project pack → user pack → builtin; not gated by acknowledgePromptsRisk. |
| `compress.tiers` | boolean | true | — | Tiered T1→T3 distillation spreads folding cost across generations. |
| `compress.protectedTools` | string[] | none | — | Hard exclusion across all history: results of listed tools never fold. Path patterns (skill/<name>) select skills by name (#1947). |
| `compress.protectedLatestTools` | string[] | none | — | Protects only the LATEST instance of cumulative-snapshot tools whose newest result supersedes older ones (e.g. todo lists). Path patterns keep the latest instance per skill (skill/*, #1947). |
Expand Down
4 changes: 2 additions & 2 deletions CONFIGURATION.zh-CN.md
Original file line number Diff line number Diff line change
Expand Up @@ -181,7 +181,7 @@
| `guardrails` | object | {} (all defaults) | — | 守卫集合:pi/omp 插件的工具输出守卫(#3066)及代理侧流式 text-run 守卫(#3406)。 |
| `guardrails.bashTimeout` | number | 60 | BILI_GUARDRAIL_BASH_TIMEOUT | 模型未写 timeout 时注入到 bash 工具的秒数(#3066 owner 有意为之,#3366 重申:无人看管的 bash 会把 pi 会话挂死一整天——宿主 schema 本身无默认值)。设 N 调整秒数,设 0 关闭注入(恢复 pi 原生行为)。 |
| `guardrails.maxOutputBytes` | number | 50000 | BILI_GUARDRAIL_MAX_OUTPUT_BYTES | pi/omp 插件中每个工具结果的文本输出合计字节上限(0 禁用)。超限输出从头截断并附指向宿主已存完整输出的提示。 |
| `guardrails.repetition` | boolean | true | BILI_GUARDRAIL_REPETITION | pi/omp 插件的同一调用循环破除器(连续 3 次警告、5 次中止,按字节全同判定)。false 或 env 0 关闭。 |
| `guardrails.repetition` | boolean | true | BILI_GUARDRAIL_REPETITION | pi/omp 插件的同一调用循环破除器:连续第 3 次起随结果附警告;第 5 次只拒绝这一次调用并发出明确的最后警告(回合保留,合法的等待/轮询此时可改成一次更长的等待继续);被拒之后仍一字不差地重发同样调用才终止整个回合(#5225)。false 或 env 0 关闭。 |
| `guardrails.textRunThreshold` | number | 200 | BILI_GUARDRAIL_TEXT_RUN_THRESHOLD | 响应流上解码后模型文本的单字符重复破除器(#3260;#3331 审查后由 #3406 第 1 项补上开关)。连续 N 个相同码点即触发——正常文本远低于默认 200,符号循环的模型会撞上。设 N 调整阈值,设 0(或负数)关闭:合法的长同字符输出(代码注释分隔线、ASCII 分隔线)不会再被中途掐断。thinking/reasoning 通道也在该守卫内。 |
| `persist` | object | {} (all defaults) | — | 会话落盘持久化(XDG state 目录之下)。 |
| `persist.enabled` | boolean | true | BILI_PERSIST | 会话记录落盘总开关(0/false 关闭)。 |
Expand Down Expand Up @@ -275,7 +275,7 @@
| `compress.maxSummaryLength` | number | kernel 20000 | — | 单条生成摘要的硬字符上限;超长的回复被整段拒绝(不截断、不重试)。外部摘要模型会被提前告知这个确切上限(#3635)。0 = 不限制。 |
| `compress.minSummaryLength` | number | kernel 50 | — | 生成摘要的字符下限;过短的回复被整段拒绝。0 = 禁用。外部摘要模型受同一下限约束(#3635)。 |
| `compress.reconcile` | "off" \| "warn" \| "repair" | "repair" | BILI_FOLD_RECONCILE | 客户端在轮次之间回退或改写历史时校准已折叠状态。 |
| `compress.promptPack` | string (builtin: "default", "lean", "chat") | builtin "default" | — | 压缩提示词包,按 项目包 → 用户包 → 随包附带(chat)→ 内置 解析;不受 acknowledgePromptsRisk 门控。 |
| `compress.promptPack` | string (builtin: "default", "lean") | builtin "default" | — | 压缩提示词包,按 项目包 → 用户包 → 内置 解析;不受 acknowledgePromptsRisk 门控。 |
| `compress.tiers` | boolean | true | — | T1→T3 分级蒸馏把折叠成本摊到多代。 |
| `compress.protectedTools` | string[] | none | — | 全历史硬排除:列出工具的结果永不折叠。路径模式(skill/<name>)可按名指定 skill(#1947)。 |
| `compress.protectedLatestTools` | string[] | none | — | 只保护累积快照类工具「最新一次」实例(新结果覆盖旧结果的工具,如 todo 列表)。路径模式按 skill 分组各保最新(skill/*,#1947)。 |
Expand Down
2 changes: 1 addition & 1 deletion LIFECYCLE.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,6 @@
| `BILI_OPENCODE_INLINE` | #3278 opencode 移植(#4687) | opencode inline 模式(需手动开启,默认保持旧行为 spawn,owner 决定不改默认):与 pi 同构——不起 proxy 进程,模型 URL 被 V2 route/intercept 改写成伪 origin 后由进程内引擎接住(bun 宿主已验:引擎 boot/dispatch 全绿);`=1/on/yes/TRUE` 或 file 家 `"opencode": {"inline": true}` 显式开启(显式开启压过 attach 目标);`bili opencode-inline` 一键车道 | 同 pi inline 车道节奏 | opt-in(不设置时 attach/spawn 行为与旧版完全一致) |
| `BILI_INLINE_DEBUG` | #4669 | 仅 inline 车道:引擎 stderr 日志腿默认静默(stderr 是 pi 的交互终端,日志会挤掉输入框;默认只写 bili.log),设 1 恢复 stderr 输出用于排查 | 随 inline 车道(#3278)走 | 排查逃生口 |
| 测试钩子:`BILI_DSH_RECOVERY_INTERVAL_MS` / `BILI_DSH_RETRY_INTERVAL_MS` / `BILI_MODEL_INFO_RETRY_MS` | #2082 等 | 缩短测试/运维节奏(dsh-native.ts;NODE_TEST_CONTEXT 感知,避免生产误缩) | 永久测试设施,随宿主代码走 | 测试钩子 |
| `BILI_SESSION_CONTENT_STORE_PIN` | #4788 phase 2(c8d7a802) | idle-fold 逃生口:`=1/true` 让每会话 CCR content store({byRef}/{byHash} 原文)常驻内存、save 落盘后不折叠(默认折叠;读点 src/knobs.ts:451,store 可从 unified ccr mirror 或 .content-store.json sidecar 重新物化) | #4788 phase 2 idle-fold 生产站稳后评估退役(owner 拍板) | 在用(默认 fold) |

## 2. 常设面全量登记表(src/ 实际读取的其余 BILI_* 环境变量)

Expand Down Expand Up @@ -125,6 +124,7 @@
| `BILI_SESSION_GC_INTERVAL_MS` / `BILI_SESSION_GC_MAX_AGE_DAYS` / `BILI_SESSION_GC_MAX_TOKENS` | 会话 GC 参数(默认 1h / 7d / 1M tokens) |
| `BILI_SESSION_RESIDENT_MAX_BYTES` | sessions.residentMaxBytes,512 MiB 软上限(#2803) |
| `BILI_SESSION_RESIDENT_HARD_MAX_BYTES` | sessions.hardMaxBytes,单会话驻留字节硬上限(#4788 D1-A);默认同 residentMaxBytes(512 MiB),设 0 关闭——补软上限对唯一活跃会话的盲区 |
| `BILI_SESSION_CONTENT_STORE_PIN` | `=1/true` 保持单会话 CCR 内容存储(byRef/byHash 原文)常驻内存不折叠(#4788 phase 2 / #3916-E;首次触摸时从 unified ccr 镜像或 .content-store.json 侧车重建);缺省/0/false = 落盘后折叠(默认) |
| `BILI_SESSION_WARM_MAX_BYTES` | warm 解码字节上限,64 MiB(#2803) |
| `BILI_PERSIST` | `=0` 关闭持久化(ephemeral/test) |
| `BILI_PERSIST_DEBOUNCE_MS` | persist.debounceMs,500 |
Expand Down
Loading
Loading