Force resync - A possible albeit late GSoC idea?

[tangodelta]

Hello,

I've searched this category and github, but couldn't find anything like that.

Yesterday I had an issue where my Joplin instances became out of sync. The reason probably was that I closed my laptop too fast before switching to my PC. Nextcloud synced all files, but Joplin got confused by timestamps. At least that's my understanding of it. See here:

Understanding syncing process

I have a question about that process. I discribe what I suppose the processs does, correct me when I'm wrong If I create 10 notes with 10 ressources each, Joplin will sync all of them with the cloud service. I decide to drop all that 10 notes , because that was for a test, Joplin syncs that too. What's happened on the mobile ? Does joplin do nothing because the 10 creations and 10 deletions of the same notes, cancel themselves ? Joplin creates the 10 notes on the mobile and …

Sync issues using filesystem sync and sync tool

We sync using Joplin's filesystem sync and an external sync tool. Sometimes things get messed up. Sometimes another persons edits are not synced to my machine. (Maybe some rare sync conflicts are also related.) Most recent case: yesterday. I figured out that "touch *" (bash command) in the filesystem sync folder motivates Joplin to reexamine all the files. Missing notes appear. But is there a better way than this workaround? Maybe enable Joplin to be more thorough in examining sy…

I had to touch * in the ~/Nextcloud/Joplin folder and that (after a full resync) seemed to have fixed the issue. This simple fix took IMHO far too long to find and while I had the patience and tech skills to use it, more casual users may not.

So, how about some button that would do the same thing? Stupid things can happen, the users' sync tool of choice may glitch out, something else may crash etc. Also: Windows users may not have access to touch, I'm not sure here.

The way I see it, Joplin would display a warning, that this would cause a full resync of all notes, which may take time on bigger installations. Also, the user may get hit by throttling by the cloud provider ('cause Joplin creates thousands of small files).

What do you think?

[nerati]

Makes sense to me.
(Regarding throttling, it may not be an issue, as we’re mostly talking about Joplin re-importing from the local file system sync. At least that is what touch * triggers as far as I understand.)

[michelb]

I can only support a "full resync" option. I encountered an issue with the joplin server where I incorrectly setup something in docker and now I need to do a full resync on all clients. Only, that isn't possible apparently. I have to export all notes apparently and then reimport them all in 1 client.
The stupid thing is that that when I try to sync, the joplin desktop says that a resync is required. It just doesn't do it.