Hello,
I noticed that the command "jotta-cli sync log" seems to have started listing events in a reverse order.
If I remember correctly, it used to show the events in a chronological order so that the newest event was listed last, but now the oldest event is showed last instead and new events need to be brought up using the -n option with a large enough value so that the newest row can be seen. This threw me off for a bit while trying to check if the sync has been working properly, since the default output only listed events from couple months ago and would never update although any new changes to files seemed to be syncing just fine when looking at the web ui.
Maybe this has changed in recent versions or perhaps it's just my memory letting me down? It's not a huge deal but at least I don't remember having to use the -n option (nor piping to 'head') before. I have been using 0.17.148769 for a while but just updated to 0.17.159692, though the upgrade made no difference on the output order.
$ jotta-cli sync log
2026-02-09 21:15:43.142 +0200 EET :: Finished
2026-02-09 21:15:43.139 +0200 EET :: Upload /{{ REDACTED }}/{{ REDACTED }}
2026-02-09 21:15:43.023 +0200 EET :: Upload /{{ REDACTED }}/{{ REDACTED }}
2026-02-09 21:15:42.321 +0200 EET :: Upload /{{ REDACTED }}/{{ REDACTED }}
2026-02-08 21:15:37.091 +0200 EET :: Finished
2026-02-08 21:15:37.087 +0200 EET :: Upload /{{ REDACTED }}/{{ REDACTED }}
2026-02-08 21:15:36.968 +0200 EET :: Upload /{{ REDACTED }}/{{ REDACTED }}
2026-02-08 21:15:35.402 +0200 EET :: Upload /{{ REDACTED }}/{{ REDACTED }}
2026-02-08 16:42:44.873 +0200 EET :: Finished
$ jotta-cli sync log -n 200|head
2026-04-02 18:31:09.576 +0300 EEST :: Finished
2026-04-02 18:31:09.57 +0300 EEST :: Download /{{ REDACTED }}/{{ REDACTED }}
2026-04-02 18:21:05.914 +0300 EEST :: Finished
2026-04-02 18:21:05.908 +0300 EEST :: DeleteFile /{{ REDACTED }}
2026-04-02 18:20:16.855 +0300 EEST :: Finished
2026-04-02 18:20:16.849 +0300 EEST :: Upload /{{ REDACTED }}/{{ REDACTED }}
2026-04-02 18:20:00.502 +0300 EEST :: Finished
2026-04-02 18:20:00.496 +0300 EEST :: Upload /{{ REDACTED }}
2026-04-02 18:16:39.61 +0300 EEST :: Finished
2026-04-02 18:16:39.605 +0300 EEST :: Upload /{{ REDACTED }}/{{ REDACTED }}
Hello,
I noticed that the command "jotta-cli sync log" seems to have started listing events in a reverse order.
If I remember correctly, it used to show the events in a chronological order so that the newest event was listed last, but now the oldest event is showed last instead and new events need to be brought up using the -n option with a large enough value so that the newest row can be seen. This threw me off for a bit while trying to check if the sync has been working properly, since the default output only listed events from couple months ago and would never update although any new changes to files seemed to be syncing just fine when looking at the web ui.
Maybe this has changed in recent versions or perhaps it's just my memory letting me down? It's not a huge deal but at least I don't remember having to use the -n option (nor piping to 'head') before. I have been using 0.17.148769 for a while but just updated to 0.17.159692, though the upgrade made no difference on the output order.