-
Notifications
You must be signed in to change notification settings - Fork 671
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
easy setup to sync within a sync folder #6654
Comments
Well, we can't prevent the user to do every stupid things. We could guard against syncing a folder or one of its subfolder which is already shared with a local folder or one of its parent folder of the same account. This would catch some of these wierd issues. There would still be ways to introduce loops with other accounts, but we IMHO don't need to go to great length to prevent that. |
I found it "too easy", because the user interface seems to guide me into that situation. I know that a 'Add Folder Sync Connection' is something different. But I fear that most users don't realize that, when they see |
@jnweiger Unrelated, but your screenshot do not have the '...' icon. Seems like the svg plugin is missing. |
…er points to deleted folders Note that we also needed to adjust the server url to contains the user name in the folder wizard. (As checkPathValidityForNewFolder expect the user name) Issue #6654
The logic to avoid this kind of problem was already there. But it did not work correctly when there was existing folder with deleted directory. Fixed in #6656 |
…er points to deleted folders Note that we also needed to adjust the server url to contains the user name in the folder wizard. (As checkPathValidityForNewFolder expect the user name) Issue #6654
…er points to deleted folders Note that we also needed to adjust the server url to contains the user name in the folder wizard. (As checkPathValidityForNewFolder expect the user name) Issue #6654
…er points to deleted folders Note that we also needed to adjust the server url to contains the user name in the folder wizard. (As checkPathValidityForNewFolder expect the user name) Issue #6654
@ogoffart looks like I can run two owncloud clients in parallel in the same sync folder now. |
Tested with 242~rc1 on ubuntu 18.04 and testpilotcloud version 2.6.0daily20180713 (build 9853)
DO NOT DO THAT ON A PRODUCTION SYSTEM
Expected behavior: it should not be possible to have two syncs in the same folder running at the same time.
Observed: It is quite easy to do so, one client is sufficient. Havoc results, replicating the same folders inside the toplevel folder again and again, probably until MAXPATHLEN or diskquota are exhausted.
Reproduce:
testpilotcloud &
rm -rf ~/testpilotcloud
testpilotcloud &
and notice the expected error message:/home/USERNAME/testpilotcloud
Documents
-> Next -> Add Sync ConnectionNow we have two active sync connections. The client window alternates between
and
The top level folder gets synced into the Documents folder with every rediscovery loop, generating a deep hierarchy of
There are two .sync*.db datastructures in the same folder. Both active
DO NOT DO THAT ON A PRODUCTION SYSTEM
The text was updated successfully, but these errors were encountered: