This repository was archived by the owner on Nov 7, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 7, 2022. It is now read-only.
sync fail when a new directory exists and it is not empty #39
Description
Hi,
This:
$ mkdir .diff/foo
$ touch .diff/foo/bar
$ dropbox-api sync .diff dropbox:/diffs/ -d
upload foo/bar /diffs/foo/bar
mktree foo /diffs/foo
2018-02-14T13:40:43 [WebService::Dropbox] [ERROR] https://api.dropboxapi.com/2/files/create_folder {"path":"/diffs/foo"} -> [409] {"error_summary": "path/conflict/folder/..", "error": {".tag": "path", "path": {".tag": "conflict", "conflict": {".tag": "folder"}}}} at /usr/local/lib/perl5/site_perl/WebService/Dropbox.pm line 184.
{"error_summary": "path/conflict/folder/..", "error": {".tag": "path", "path": {".tag": "conflict", "conflict": {".tag": "folder"}}}} at /usr/local/bin/dropbox-api line 1014.
I am not quite sure why this happens, but what seems to happen is that it first uploads foo/bar, which creates the foo directory automatically, and then, it tries to create the foo directory and fails because it is already there.
Activity
mat813 commentedon Feb 15, 2018
Mmmm, and I get a similar problem when removing a non empty directory, it removes files in a random order, and removes the directory before removing all its content, and then tries to remove the last file, and fails because it went away with the directory.