You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the user aborts the upload in some way, for example by clicking the "Cancel" button during upload, the server does not correctly close the upload pipeline.
Steps to reproduce
start the server in dev mode (following instructions in readme)
start uploading a large file
interrupt upload
see that there is a file in the uploads folder (which should be normally deleted on this line)
run lsof -p <pid> and see that the file is still open (this blocks automatic deletion by an external script! File does not get actually deleted from fs until the descriptor is closed...)
be sad :(
The text was updated successfully, but these errors were encountered:
Ok I managed to create a hotfix for our instance. .pipe() does not properly propagate errors, and on top of that, the ws stream is not properly closed.
If you've been running send for a long time with a bit of traffic, then I recommend running fsck on the filesystem where you store files. This reclaimed multiple hundreds of gigs of disk space for us. I assume ext4 did not like all the open but deleted files.
If the user aborts the upload in some way, for example by clicking the "Cancel" button during upload, the server does not correctly close the upload pipeline.
Steps to reproduce
lsof -p <pid>
and see that the file is still open (this blocks automatic deletion by an external script! File does not get actually deleted from fs until the descriptor is closed...)The text was updated successfully, but these errors were encountered: