Sergey KozyrenkoandClaude Opus 4.8 9e8ee58786 fix(resources,flowfiles): propagate zip Close() error instead of swallowing it ...

The four Zip* builders deferred zw.Close() with an unnamed return, dropping the
error from the central-directory flush. After the resources download moved to
direct socket streaming, a dropped connection during that final flush could
return a truncated archive under HTTP 200. Capture Close() via a named return so
streamZipArchive logs and aborts the partial response. Regression tests in both
packages drive the Close() error path with a failing writer.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-24 09:48:45 +07:00

..

files_test.go

fix(resources,flowfiles): propagate zip Close() error instead of swallowing it

2026-06-24 09:48:45 +07:00

files.go

fix(resources,flowfiles): propagate zip Close() error instead of swallowing it

2026-06-24 09:48:45 +07:00