Skip to content
This repository was archived by the owner on Jan 20, 2025. It is now read-only.

fix: emit new event specifically when all data has been written to disk #8

Merged
merged 1 commit into from
Oct 21, 2021

Conversation

addaleax
Copy link
Contributor

The finish event on the target Writable itself would not indicate
this when gzip compression is being used, because the gzip stream
could finish before the subsequent fs.write call to the actual
target file was completed. This could truncate the file in cases
where the application quits immediately after the 'finish' event
was emitted.

The `finish` event on the target Writable itself would not indicate
this when gzip compression is being used, because the gzip stream
could finish before the subsequent `fs.write` call to the actual
target file was completed. This could truncate the file in cases
where the application quits immediately after the 'finish' event
was emitted.
@addaleax addaleax merged commit 2050e01 into main Oct 21, 2021
@addaleax addaleax deleted the account-for-gzip-flush branch October 21, 2021 11:53
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant