Repository navigation
[PR] batch-6: 4 low-risk community fixes (verbatim --no-ff merges, authorship preserved) - #7412
Conversation
⚠️ MODEL-FACING TEXT CHANGE Failure-response host fields now mask 127-prefixed DNS names and keep a portless IPv6 loopback intact. Status, failure kind, code and retry policy are unchanged; the exact visible 502 error is covered by a regression. Require actual IPv4 loopback addresses instead of accepting any 127. prefix. Retain Node's numeric IPv4 aliases after syntax validation and canonicalization. Split bracketed display targets after their closing bracket so an address colon is never mistaken for a port separator. The unchanged base fails six behavior regressions with two controls passing. The fix passes 52 focused tests, typecheck, build and both static gates.
Create incident files exclusively so repeated same-millisecond failures, sanitized session-name collisions, and existing files cannot lose earlier evidence. Keep the historical filename when available; on EEXIST use a bounded session hint and a UUID suffix, again with exclusive creation. Use the same writer for main and preflight-summary failures. Other I/O errors retain the existing fail-soft warning/null behavior. The plaintext banner, byte limits and protected GC prefixes are unchanged. Seven regression failures on the unchanged base become passing, alongside the write-error control and existing dump/GC coverage (30 tests total). Typecheck, build, unused-export and import-graph gates pass.
Reduce trajectory and recovery-window extrema without expanding retained ledger samples into individual function arguments. Preserve every plot point, reference axis, recovery floor and outlier threshold. The unchanged base fails both 200,000-sample regressions; the fixed branch passes all 15 report and large-ledger tests, typecheck, build and static gates. This follows the separate cache-bucket fix in #6689; the SVG exporter's extrema were not covered there.
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.11103-pr.7412.c71c221This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr7412.tgz
npm install -g packageInstall instructions are refreshed on each push. |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.1241-master.b10c1a0 # this exact build
npm install -g billion-context@master # always the newest merged build
|
(ai: qwen/qwen3.8-27b) 查重: 不重复。这是 batch-6 批次 PR(GitHub #7412),把 4 个已独立 review 的社区 fix(#7393/#7397/#7400/#7404)用 Review 结论:可合(待 CI 测试分片跑绿)。 4 个 fix 逐一审过——逻辑正确、测试有牙、diff 干净、作者署名保留、唯一的 model-facing 文本变更已披露。 What I verified (independent of the PR's own claims):
八问(结构化结论):
合并判定:可合。 代码、测试、diff、署名、披露全部过关;唯一待办是 CI 的 9 个 |
batch-6: 4 low-risk community fixes (verbatim
--no-ffmerges, authorship preserved)One batch PR carrying 4 independently-reviewed, self-contained fixes by Afloat. Each is a scoped bugfix with a regression test — no design-level change, no hot-path/core file touched (URL masking, diagnostics, one report exporter).
This is batch-6 of the layered split that began with batch-5 (#7392, merged): the small, isolated fixes come here in one reviewable unit; the remaining load-bearing ones (loop adapters / billing / storage / session-gc / persistence / keepalive, plus
relay.ts/stream-io.ts/plugin.tshot paths) stay separate so each gets its own focused review.How the merges preserve authorship (and auto-close the source PRs)
Each PR is brought in with
git merge --no-ff <its head>— the original commit SHAs, author (Afloat), dates, messages, and content are preserved verbatim in this branch's history (not squashed, not cherry-picked). Because each source PR's head commit becomes an ancestor of master once this lands, GitHub flips all 4 source PRs to "merged" automatically — no manual closing, no duplicate landings.What's in it (4)
127.-prefixed string, so private DNS names like127.customer.internalleaked through diagnostic URLs, host-event files, and 502 upstream-failure responses even with host masking on. Only a real 127/8 IPv4 loopback literal is now exempt.hostnow shows the masked form (acp-proxy failure: dns ENOTFOUND <private-host>:8443), not the private name.writeFileSyncoverwrote an earlier incident when those values collided — silently losing evidence that is explicitly protected from retention GC. Both writers now create the file exclusively; only onEEXISTdo they fall back to a UUID-suffixed name.Math.max.apply, so a legitimate 200,000-sample history threwRangeError: Maximum call stack size exceededbefore the report could be downloaded (three more extrema calls in the recovery chart had the same ceiling). Those maxima/extrema are now computed with reductions; every sample still renders.著作权 (authorship)
All 4 source PRs are by Afloat (
ShuffleMonkey@163.com); their original commits are preserved verbatim viagit merge --no-ff(author, date, message, content intact). 8 files changed, +388 / −26, 4 merge commits. No conflicts at assembly time (the single intra-batch overlap —src/log-mask.tsfrom #7393 + #7397 — merged cleanly).Verification
tsc --noEmit+npm run build: clean (dist import / external / thin checks OK).log-mask-linear,issue5795-early-hold-fastpath,loopback-diagnostic-hosts,error-dump-collision,session-report): 54 pass / 0 fail.After this merges
The 4 source PRs — #7393 #7397 #7400 #7404 — land with content identical to theirs and will auto-flip to "merged" (their head commits are ancestors of master). Nothing needs manual closing.
Fixes #7391, fixes #7396, fixes #7399, fixes #7403.