to ensure compatibility with Widnows, we will remove automatically the
leading space characters in file name of new files or folders
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
Use std::prev for it rather than -1 in Syncengine
Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
take is deprecated in scoped pointer
Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
f handle
Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
Use unique_ptr instead of scoped pointer for propagator firstJob
Fixes deprecation warning
Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
Use unique_ptr for discoveryphase, replace take with release
Fix deprecation warn
Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
f unique
Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
past versions may have wrongly set the write permissions for other users
(UNIX style permissions)
remove this under the hypothesis that newly created files or folders
gets more restrictive permissions and that past files or folders should
be updated to get the same permissions
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
should hopefully allows to understand when local file system discovery
is done or omitted
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
will enable implementation of other ways to interrupt sync after
discovery to get user feedback
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
sometime we need to create a folder on server because some local files
or folders modifications would be lost without that
in that case instead of locally deleting teh folder, we create it back
on server
when doing that, it is important to check the remote permissions such
that we do not try to create a folder in a read-only folder on server
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
The signal is not connected to any slot when running nextcloudcmd.
The callback to finish the sync was never being called because the check for the config was done in the slot,
which was never called.
Signed-off-by: Camila Ayres <hello@camilasan.com>
avoid single file sync to switch to data fingerprint restore sync mode if
a data fingerprint has been saved in the database but missed during
single file sync
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
in case sync would complete after a data fingerprint change, we should
tolerate some errors
a file being blacklisted for whatever reason should not block the
propagation of data fingerprint
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
we should not try to restore files/folders no longer synced because of
selective sync when detecting a data fingerprint change
in case the user deselect a folder from selective sync list, we would do
a local delete
in case the client is also detecting a change of data fingerprint (or is
stuck in restore mode) then instead of applying the new set of selected
folders to sync, it would upload unselected files/folders
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
