Repository navigation
npm registry: 128 MiB decoded cap, gzip, visible failure reasons (pilot false block) - #21
Conversation
… failure reasons (K-18) vite's full packument (37.2 MiB) was over the 32 MiB cap and gave a false hard block on front-end PR 2027. Collect now logs each failed lookup. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
… cap (K-19) renovate's full packument is about 74 MB and grows. The fetcher now sends Accept-Encoding: gzip, inflates in bounded steps, counts decoded bytes against the cap and the run budget, and fails closed on other encodings or bad gzip. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…arrives (K-19 fix 1) A timeout or network error no longer spends the run budget; oversize and bad-encoding downloads still count. Near the budget an over-grant response maps to the byte-budget reason. Docs: encoding reason in the reason order, note on decoded-byte budget. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
🔴 FAIL: OC Claude review did not completeCaution Incomplete file coverage blocks this PR. No waiver can clear it.
Run 40943446648, attempt 1 for head 📋 Full review record: reasons, checks, signals, finding details, model summaries, token usageReviewed snapshot
Reasons the gate failed
No waiver line is shown. At least one reason cannot be waived, so a waiver would not change the result. Checks (code, no model)
Signals (context only, never block)
Dependency changes None. Finding details
Blocking is decided by code from category and severity, never by the model. A finding in a blocking category blocks only at high or critical severity. No findings from the passes that ran. The Review, Security, Supply chain pass did not run, so this is not a clean result. Model summaries
Token usage
|
Fixes the third pilot false result on front-end#2027: "dependency data incomplete: registry lookup failed" for vite@8.3.5 (a real version). The full npm document for
viteis about 39 MB; the 32 MiB cap rejected it, and the job log did not say why.NPM_MAX_RESPONSE_BYTES32 -> 128 MiB (decoded). Largest legitimate document measured: renovate, about 74 MB, growing about 22 MB/yr; 128 MiB keeps 8 parallel full parses within runner memory.time[v]and lifecycle scripts, with its trigger (a legitimate document near 100 MiB, or runner memory pressure). The owner chose this route after two independent analyses; evaluate in the pilot before a larger change.Unit tests 2701 passed; release tests 2 passed. Live check: real vite document fetched with gzip parses and yields time["8.3.5"]. Eval not run.
Review: one fix round (budget reservation on failed fetches), scoped re-review clean. Open minor: a fetch that streams most of a body then fails counts 0 bytes against the run budget (bounded by the per-fetch timeout and the 240 s run budget).
Goes live only with a release.
🤖 Generated with Claude Code