I use automatic sync and I observed syncing was no longer working and state difference between various machines and also the web client.
I ran run_jottad && jotta-cli sync stop && jotta-cli sync trigger, which returned:
ERROR Could not perform triggered sync: /dj-samples/Legacy/SoundFont2 Waves/Applause Samples already exists with different case: Case Collision in tree
- So it seems some part of the infrastructure is case insensitive and can't handle multiple directories or files with the same name different case.
- Why is jotta-cli not skipping the file and continuing with the sync?
- If I hadn't manually triggered a sync I wouldn't have known because according to
jotta-cli status sync didn't show any errors.
I wrote a gist: https://gist.github.com/svandragt/a83803cbb6ef29f9df6b45b1eb28d63f to resolve this locally, after that I was able to resume syncing, but I am concerned now that this may happen again in the future.
$ jotta-cli version
jotta-cli version 0.17.159692
$ neofetch
OS: elementary OS 8 x86_64
Host: Micro-Star International Co., Ltd. PRO X670-P WIFI (MS-7D67)
Kernel: 6.17.0-14-generic
Uptime: 4 hours, 17 mins
Packages: 2859 (dpkg), 71 (nix-default), 62 (flatpak)
Shell: zsh 5.9
Resolution: 1920x1080, 1920x1080
DE: Pantheon
WM: Mutter(Gala)
Theme: io.elementary.stylesheet.blueberry [GTK3]
Icons: elementary [GTK3]
Terminal: devbox
CPU: AMD Ryzen 9 7900X3D (24) @ 5.663GHz
GPU: AMD ATI Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT
Memory: 21760MiB / 31763MiB
I use automatic sync and I observed syncing was no longer working and state difference between various machines and also the web client.
I ran
run_jottad && jotta-cli sync stop && jotta-cli sync trigger, which returned:jotta-cli statussync didn't show any errors.I wrote a gist: https://gist.github.com/svandragt/a83803cbb6ef29f9df6b45b1eb28d63f to resolve this locally, after that I was able to resume syncing, but I am concerned now that this may happen again in the future.