vorotamoroz
vorotamoroz
Sorry for being late! This problem has been fixed at v0.24.0. And, `Rebuild everything` is the best way bring everything back to fine! (But it were possibly a bit of...
Thank you for opening the Issue! I am so sorry for the inconvenience! There seems to be a problem with chunks not being sent properly these days. This is being...
As Postscript, possibly disabling `Send chunks in bulk` or enabling `Compute revisions of chunks` sometimes works. But I am still not sure (So, rewriting and writing tests also this now)....
This problem has been fixed at v0.24.0. And, Rebuild everything is the best way bring everything back to fine. Or https://github.com/vrtmrz/obsidian-livesync/issues/510#issuecomment-2411647763 will fix the vault. Would you mind if I...
ご報告ありがとうございます、0.24.0でも発生していましたか… 最初の同期で発生するのは少し納得がいきますね。Recreateしても、作成順は変わらないので、これは初回同期の修正には役立たないかもしれません。ご案内ミスですね。本来はRebuild everythingが必要だったのだと思います。ただ、微妙なところで、Fetch chunks on demandがちゃんと待ってない可能性もあるのかも。。 おそらくE2EEを無効化したタイミングでRebuild Everythingをしているので、それでようやくDBの整合性が合った可能性もあります。 なので、再度E2EEを有効にしても（また Rebuild Everythingされるので）問題無く同期できると思いますが、対策として、チャンク収集部分を少し修正してみようと思います。 また、状況が良くなった際には告知しますので、よろしくお願いいたします。 --- Thank you for reporting this! So sorry to hear that it have been still occur in 0.24.0......
Sorry for being late! `Fetch again has been scheduled` indicates that your vault is scheduled to be reconstructed with the remote database. Therefore, your local changes will be discarded and...
Thank you for opening the issue! As you mentioned, the difference between `Sync on Save` and `Sync on Editor Save` is reacting to storage events or UI events (which were...
Sorry for being late! Your comment is quite correct. But I have had less time to maintain that. However, now [Kohki has been joined to the team](https://github.com/vrtmrz/obsidian-livesync/discussions/560), and the documentation...
Sorry for being late! And thank you for opening the issue! However, your configuration seems fine. Would you mind if I ask you to enable `Verbose log` and check what...
Thank you for opening the issue! I did not track the latest version! `${node}` can be retrieved from `https://couchdb.example.com/_membership` as following (probably): ```json {"all_nodes":["nonode@nohost"],"cluster_nodes":["nonode@nohost"]} ``` If we set up CouchDB...