retry when upload fail about dufs HOT 9 CLOSED

Issue #95 is open to handle concurrency.

from dufs.

why so many failures, could you post logs？

I don't support retries because:

1. Failure is a rare case.
2. Re-upload requires allow-delete.

from dufs.

weird. I did the identical uploading again, and got two failures.

……
……
Duplicate.Cleaner.Pro.5.16.0.0/Magick.NET-Q8-AnyCPU.dll ✗
……
……
Duplicate.Cleaner.Pro.5.16.0.0/x64/SQLite.Interop.dll ✗
……
……

Then the log during this uploading:

……
……
[2022-07-05T05:21:13.130Z INFO] 192.168.123.221 "PUT /Duplicate.Cleaner.Pro.5.16.0.0/Magick.NET-Q8-AnyCPU.dll" - 201
……
……
[2022-07-05T05:22:39.590Z INFO] 192.168.123.221 "PUT /Duplicate.Cleaner.Pro.5.16.0.0/x86/SQLite.Interop.dll" - 201
……
……

Finally after I refresh the web page, these files do exists, so are in the local file system.
Seems the error only appears on the web page.

from dufs.

ui should not show failure if log shows success.

Could you open webdev tools and take a screenshot of the network/console panel?

from dufs.

sure, I take one of the failures as example.

web page result:
Duplicate.Cleaner.Pro.5.16.0.0/Magick.NET.Core.dll ✗

backend log:
[2022-07-05T10:27:48.897Z INFO] 192.168.123.221 "PUT /Duplicate.Cleaner.Pro.5.16.0.0/Magick.NET.Core.dll" - 201

webdev network:

webdev console:

from dufs.

dufs never returns 502. Are your run dufs behind a proxy?

from dufs.

Yes, I deploy dufs on my local machine, and expose the service through frp(a reverse proxy).
Then access by the public ip and port.
Could this be the reason?

from dufs.

The probability of upload failure is related to network quality and concurrency.

You can test whether reducing the concurrency can improve the upload success rate.

from dufs.

sure, I will try.
And Since it's not the problem of program itself, I think this thread could be closed.
Thanks for your tech support :)

from dufs.