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
I've noticed that after a failed upload, subsequent retries fail because of a name collision.
If I sync again, I can find the file and see that it has been created, then I trash it and can upload it again.
So it looks like an entry in the local cache should be added after a failed upload, or maybe even auto-trash the file, because the file has been created in ACD, but the content is truncated.
Look at this duplicity bug report, where I paste the exact errors.
I've noticed that after a failed upload, subsequent retries fail because of a name collision.
If I sync again, I can find the file and see that it has been created, then I trash it and can upload it again.
So it looks like an entry in the local cache should be added after a failed upload, or maybe even auto-trash the file, because the file has been created in ACD, but the content is truncated.
Look at this duplicity bug report, where I paste the exact errors.
https://bugs.launchpad.net/duplicity/+bug/1640195
I use duplicity which calls acd_cli to upload the files. In this example, the command that failed was:
In the first attempt, it failed with this error:
The next retries were all failing with a name collision error:
The versions used are:
The text was updated successfully, but these errors were encountered: