Manage Subfolder Sync Randomly does nothing
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.5k
- Forks
- 692
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 23
Description
Describe the bug
I have a shared workspace.
I have multiple folders and subfolders, varying in size between 1gb to 200gb.
When I choose the option to manually sync subfolders, sometimes it will sync if i turn the check mark on. Sometimes it will say everything is synced but nothing syncs at all.
For example, I have a folder structure like: Design\Ads\2022 and Design\Ads\2023 (so on and so on for each year)
I choose to sync folder 2023 and it says 'synced' but nothing happens.
However, sometimes if I just create a new folder in the 2023 folder, it could be any empty folder, it starts to trigger some sort of refresh and it starts to sync.
I have tried manually forcing the sync, I have tried closing owncloud and opening it back up, but this issue still happens.
Steps to reproduce
- Open owncloud and select manual subfolder sync
- Turn on a folder to sync
- Wait for hours and hours and nothing syncs, even though the workspace says its synced
Expected behavior
Should just start syncing after clicking check mark to sync folder.
Setup
- Owncloud Infinite Scale 8.2, running in docker
- Owncloud desktop client on both mac and windows version 7.1
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
Start at the desktop client's manual subfolder sync flow and reproduce the issue with the listed ownCloud Infinite Scale, macOS, or Windows versions. Trace why selecting a folder reports it as synced without transferring files, then verify that selecting a subfolder reliably starts synchronization without needing a new folder or other refresh trigger.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100