Please warn users before activating Virtual Files
- Dominant language
- C++
- Stars
- 3.9k
- Forks
- 1k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 127
Description
I wanted to test the "Virtual Files" Feature and activated it on my Windows Client.
What happened afterwards was not what I expected:
- Nextcloud started to download virtual files for all external mounts in my Nextcloud Server, this summed up to 1.6 Million Files, 9 TB of data
- I left the Client running for 4 days, but it was only 60% finished
- the `.db-wal` grew to 31 GB
I removed the Virtual Files at this stage. Please allow an option to be either selectively which folders to sync in combination with Virtual files or warn users, based on some file number limit, before enabling this feature.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by examining how Virtual Files is activated on the Windows client and reproduce the external-mount download behavior; done requires an agreed choice between selective synchronization and a warning based on file count, followed by validation that activation no longer causes an unexpected large download.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100