Sync fails after renaming a local folder with owncloudcmd
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.5k
- Forks
- 692
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 23
Description
Pre-submission Checks
- I checked for similar issues, but could not find any. I also checked the closed issues. I could not contribute additional information to any existing issue.
- I will take the time to fill in all the required fields. I know that the bug report may be dismissed otherwise due to lack of information.
Describe the bug
When attempting to move or rename a local directory that has been previously synchronized to a Space using the owncloudcmd command, the synchronization process fails to properly update the remote Space.
Expected behavior
owncloudcmd should detect that the local directory has been renamed or moved and update the corresponding folder in the Space accordingly. The synchronization should complete successfully without creating duplicates or leaving orphaned entries on the server.
Steps to reproduce the issue
- Synchronize a local directory to a folder in a Space using the command:
owncloudcmd --non-interactive -u USER -p TOKEN --server https://ocis.owncloud.com /PATH/LOCAL 'https://WebDav_URL_SPACE' REMOTE_FOLDER_IN_SPACE - Rename a local directory
- Retry the synchronization
Screenshots
No response
Logs
Could not complete propagation of "renamed_folder" by OCC::PropagateIgnoreJob(0x13b94940) with status OCC::SyncFileItem::BlacklistedError and error: "Server replied "409 Conflict" to "MOVE (skipped due to earlier error, trying again in 2 minute(s))"
...
[ warning default ]: Failed to sync
Client version number
ownCloud 6.0.0.17092
Desktop environment (Linux only)
Ubuntu 22.04.5 LTS.
Client package version and origin (Linux only)
No response
Installation path (Windows only)
No response
Server information
Infinite Scale 7.2.0 Community
ownCloud Web UI 12.0.2
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the rename scenario with the documented owncloudcmd command and inspect the PropagateIgnoreJob failure showing a 409 Conflict during MOVE. Compare the local rename with the remote Space state and retry behavior; done means the renamed directory synchronizes successfully without duplicate or orphaned entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100