fix(builder): report bytes during NUP extraction #1671

Merged

bronze-ff merged 1 commit from fix/nup-extraction-progress into main

2026-11-10 13:17:54 +00:00

bronze-ff commented

2026-11-10 12:53:51 +00:00

(Migrated from github.com)

Summary

Related to #1617. While the Builder is reading a NUP, its details log currently reports extraction progress only after every 5,000 completed files. Extracting one large member can leave the log unchanged for a long time.

Report bytes written and completed files after successful writes, at most once every two seconds. The same reporting applies to raw and compressed members. Quiet extraction, final totals and partial-file cleanup keep their existing behavior.

Validation

The regression uses synthetic NUPs and an injected clock. On main a single 24 MiB member produces no progress lines. With the change it reports the first 8 MiB while the member is still being written, skips a report inside the interval and reports again after it. The same fixture covers compressed bytes and quiet extraction.
Six related tests passed on Windows and seven on Linux, including codec, verification, path, and Builder cache coverage.
This adds diagnostics during extraction. The cause of the reported stall still needs confirmation.

## Summary Related to #1617. While the Builder is reading a NUP, its details log currently reports extraction progress only after every 5,000 completed files. Extracting one large member can leave the log unchanged for a long time. Report bytes written and completed files after successful writes, at most once every two seconds. The same reporting applies to raw and compressed members. Quiet extraction, final totals and partial-file cleanup keep their existing behavior. ## Validation - The regression uses synthetic NUPs and an injected clock. On main a single 24 MiB member produces no progress lines. With the change it reports the first 8 MiB while the member is still being written, skips a report inside the interval and reports again after it. The same fixture covers compressed bytes and quiet extraction. - Six related tests passed on Windows and seven on Linux, including codec, verification, path, and Builder cache coverage. - This adds diagnostics during extraction. The cause of the reported stall still needs confirmation.