Closed physicsdolphin closed 1 month ago
you say "manually cancel the transfer". how? if I click the button for upload cancellation, I get "1 skipped"
I see in your screenshot it says "1 failed", so I assume you did something different.
The first time when you upload a certain file, you can cancel the upload and skipped the file just as your description.
If you set 10s expiration time for unfinished upload, you'll see this up cancellation:
And after 10s you'll see the temp file is removed in web display
However, if you try to get a list by:
You'll see the temp file is not properly deleted, thus prohibiting further attempt to re-uploading the same file.
At server's end I can confirm that the temp file is not properly removed:
Then you'll have no alternative but to restart the HFS service to completely get rid of those unhandled temp file before being able to upload the same file again, or you'll be stuck like this:
After a long zero-speed timeout (Wireshark says TCP zero window which means server refused client's upload since it cannot overwrite that unhandled temp file), you'll see some "failed" hint.
ok, i see this problem is happening only on Windows
of course i made my verification, but would you care to confirm that this version is fixing the problem for you? https://github.com/user-attachments/files/17174250/hfs-windows-x64-0.54.0-alpha2.2.zip to install it you can go Admin-panel > Home and right-click on the check-for-updates
alpha3 released
BEFORE
To Reproduce
Steps to reproduce the behavior:
Describe the bug
The temporary file created whilst uploading is not correctly handled by HFS.
Expected behavior
The temporary file created whilst uploading should be correctly deleted according to settings
Screenshots
SETTINGS:
SERVER SIDE BEHAVIOR:
CLIENT-SIDE BEHAVIOR:
Environment (please complete the following information):
Additional context
Suggestions:
P.S. The HFS executable is registered on windows as a service using NSSM 2.24-103-gdee49fc 64-bit 2017-05-16, but makes no difference on this issue compared to directly running it by double-clicking the executable.