Since this one occurrence, I couldnāt reproduce this either. All Dynalist instances are working perfectly reliable. You shouldnāt waste too much time on this, until we have more info.
Itās good to know that the contents are purposefully synced independently from the location and ordering. I was just confused that the ordering of the complete list was not synced at first; then suddenly it has been synced normally.
I have one more observation: during the time where the standalone Dynalist disagreed with the on-line ordering, it produced several log files in ~/.config/Dynalist/dynalist/
:
1297 Nov 21 11:30 dynalist-2017-11-21-11-15-49.log 1879 Nov 21 12:10 dynalist-2017-11-21-11-40-32.log 595 Nov 21 13:40 dynalist-2017-11-21-13-35-11.log 4215 Nov 21 15:12 dynalist-2017-11-21-13-47-53.log 4712 Nov 21 11:12 dynalist-2017-11-21-9-47-16.log
The times are all CET.
They all contain among other messages the following error message:
[Updater] https://dynalist.io/standalone/check?platform=linux [Updater] Failed to apply updates. { Error: socket hang up at TLSSocket.onHangUp (_tls_wrap.js:1092:19) at TLSSocket.g (events.js:286:16) at emitNone (events.js:91:20) at TLSSocket.emit (events.js:185:7) at endReadableNT (_stream_readable.js:974:12) at _combinedTickCallback (internal/process/next_tick.js:74:11) at process._tickCallback (internal/process/next_tick.js:98:9) code: 'ECONNRESET' }
Is there a possibility that the (failing) update of the Dynalist standalone App is interfering with the syncing of the lists?