Config sync.interval 0 not respected

Support
1

I’m running Joplin Terminal Application. It syncs to my Nextcloud sync target after every saved change even though the timer sync is set to be disabled:

config sync.interval 0

Here are the log messages showing the sync. The timestamps begin immediately after I saved updates to a note:

 2019-12-10 14:21:50: "Scheduling sync operation..."
 2019-12-10 14:21:57: "RevisionService::maintenance: Starting..."
 2019-12-10 14:21:57: "RevisionService::maintenance: Service is enabled"
 2019-12-10 14:21:57: "RevisionService::collectRevisions: Created revisions for 1 notes"
 2019-12-10 14:21:57: "RevisionService::maintenance: Done in 132ms"
 2019-12-10 14:22:00: "SearchEngine: Updating FTS table..."
 2019-12-10 14:22:01: "SearchEngine: Updated FTS table in 246ms. Inserted: 1. Deleted: 0"
 2019-12-10 14:22:20: "Preparing scheduled sync"
 2019-12-10 14:22:20: "Starting scheduled sync"
 2019-12-10 14:22:25: "TaskQueue.stop: syncDownload: waiting for tasks to complete: 0"
 2019-12-10 14:22:25: "TaskQueue.stop: syncDownload: Done, waited for 0"
 2019-12-10 14:22:25: "Operations completed: "
 2019-12-10 14:22:25: "updateRemote: 1"
 2019-12-10 14:22:25: "createRemote: 1"
 2019-12-10 14:22:25: "Total folders: 6"
 2019-12-10 14:22:25: "Total notes: 51"
 2019-12-10 14:22:25: "Total resources: 9"

Joplin terminal application: 1.0.150 (prod)
OS: Kubuntu 19:10
Terminal application: Konsole 19.04.3
Sync target: Nextcloud

Note: I have Joplin Desktop installed on the same machine. I have not attempted to have them read/write from the same profile. Rather they sync to each other because they both point to the same Nextcloud target.

Thanks for the great application. I’ve only been using it about a week but I really love it.

2

There are 2 sync operations:

  1. a short update to the sync target when a local file changes (you can’t turn this off)
  2. a sync operation that retrieves changes from the sync target (the sync interval)
2 Likes