Multiple issues with duck.sh --synchronize
when used on a Cryptomator Vault in S3
#11113
Labels
duck.sh --synchronize
when used on a Cryptomator Vault in S3
#11113
I encountered an issue where duck.sh (version 7.4.1 (33065) on Ubuntu) removes files unexpectedly when using
--synchronize
for Cryptomator vaults in S3.How to replicate:
duck.sh --synchronize -e upload my_folder s3://my_bucket/my_vault/my_folder
duck.sh --synchronize -e upload my_folder s3://my_bucket/my_folder
againThe commands I used (with any mention of credentials removed) are listed below:
Output: "Sync complete. my_folder ↔ my_folder…"
Output: "Listing directory my_folder... test1.txt"
Output: "Sync complete. my_folder ↔ my_folder…"
Output: "Listing directory my_folder... test2.txt"
Additionally, I noticed that I am unable to use sync to download the contents of Cryptomator vaults from S3.
Entering the command:
Outputs: "Transfer incomplete. my_folder ↔ my_folder…"
I have entered variations of these sync commands with S3 buckets that are not in Cryptomator vaults and observed that duck does upload new files without deleting old files and does successfully download files with the --synchronize argument. The issue seems to only affect using --synchronize with Cryptomator vaults.
The text was updated successfully, but these errors were encountered: