mirror of
https://github.com/sigoden/dufs.git
synced 2026-04-08 16:49:02 +03:00
[GH-ISSUE #94] retry when upload fail #40
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @leolulu on GitHub (Jul 5, 2022).
Original GitHub issue: https://github.com/sigoden/dufs/issues/94
while uploading a whole folder, some files may fail.
Maybe a retry button could be helpful, or auto retry could be better.
@sigoden commented on GitHub (Jul 5, 2022):
why so many failures, could you post logs？
I don't support retries because:
allow-delete.@leolulu commented on GitHub (Jul 5, 2022):
weird. I did the identical uploading again, and got two failures.
Then the log during this uploading:
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.
@sigoden commented on GitHub (Jul 5, 2022):
ui should not show failure if log shows success.
Could you open webdev tools and take a screenshot of the network/console panel?
@leolulu commented on GitHub (Jul 5, 2022):
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:
@sigoden commented on GitHub (Jul 5, 2022):
dufs never returns 502. Are your run dufs behind a proxy?
@leolulu commented on GitHub (Jul 5, 2022):
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?
@sigoden commented on GitHub (Jul 5, 2022):
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.
@leolulu commented on GitHub (Jul 5, 2022):
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 :)
@sigoden commented on GitHub (Jul 5, 2022):
Issue #95 is open to handle concurrency.