DashboardcliZIP DIF handling, size budgets, and ove…

ZIP DIF handling, size budgets, and oversized-entry semantics

Category: gotcha
Confidence: 0.90
ID: 01a08c39-bc39-78cc-a397-d32e275ec1ed
Project ID: c760f4f9-42b0-4ce0-b36d-6b8c38d770b2
Cross-project: No
Recalled in other projects: 1
Source session: 12na8hXrpthm52Hlq
Created: 2026-06-26 11:37:10
Updated: 2026-09-10 16:49:49

Cross-Project Recalls

ProjectHitsLast recalled
opencode-lore 4 15h ago

Content

prepareZipDifs returning any non-null value, including [], means the path was handled as a ZIP; null means fall through to normal file handling because it was not a ZIP or the archive was skipped wholesale. maxZipTotalSize is a per-archive cumulative uncompressed/container budget, distinct from per-entry maxFileSize; its default is 2 GiB and 0 disables it. Pass it to readZipDifEntries as maxTotalSize. Oversized compressed entries only warn inside readZipDifEntries: their format is unknown before inflation, so they must not increment prepareDifs’ exit-driving oversizedCount. That counter is reserved for format-accurate on-disk files.

Move to: