Delays persisting tasks to DecSync CC backend

[thombles]

Tasks 13.5.1 and DecSync CC 2.2.3, both from F-Droid

When I add a task to a DecSync list it often takes a while for data to reach the disk so it can sync over SyncThing, usually a couple of minutes. This makes it a little annoying when interacting on shared task lists.

I am not precisely sure whether Tasks or DecSync CC is responsible for the delay - my initial thought is both are contributing but I would need to look at the code to be sure.

There is a useful debugging function in DecSync CC where you can tap the dots next to the task list and choose Entries count.

If there are 5 tasks initially and I add a 6th...

• During phase 1 of the delay, entries count shows Android entries: 5; DecSync entries: 5
• During phase 2 of the delay, entries count shows Android entries: 6; DecSync entries: 5
• Once both entry counts show 6, it seems to have finished persisting and it's syncing over SyncThing

What's most interesting is I can skip phase 1 of the delay if I do a pull-down-to-refresh after adding my task. If I do this, Android entries always shows 6 immediately when I switch over to DecSync CC. This makes me wonder if Tasks could do something to make DecSync CC see the change faster?

[abaker]

After you make a change Tasks starts a one minute timer. Subsequent edits reset the timer, and once it lapses it will start a sync

[thombles]

Aha that would do it. I see now, the immediate flag to the sync function.

Since I am more interested in speed than efficiency, would you be open to a contribution of a setting that would make this delay much smaller? Of course, I will have to go and see what is needed at the DecSync side too to make this nice and snappy.

(Edit to add:) Another possibility could be to observe that a given list is a DecSync backend and use minimal/no debouncing automatically since it won't have a significant impact.