Syncing often seems to be stuck at read storage processes about obsidian-livesync HOT 6 CLOSED

It might actually related to #371

from obsidian-livesync.

Thank you for reporting this issue!
I noticed this but thought it could not be that serious a problem, and pended it out. However, I was wrong.

🛫 and ⏳ indicate that detected storage changes have been queued, and are being read. It should not happen after writing to the storage. Normally, we can ignore this if the content is the same. However, this is not possible if there are conflicts in the notes.
There was also a problem with the deletion handling. These problems might have combined to cause conflict problems.

Actually, I have not reproduced the conflict problem yet, but v0.22.3 may work for it.
May I ask you to check v0.22.3, please?

from obsidian-livesync.

Hey thanks for the quick feedback!

I have updated both clients to the new version. It's still seems to be somewhat stuck though. Here are the last logs:

1/29/2024, 12:42:47 PM->Looking for the point last synchronized point.
1/29/2024, 12:42:47 PM->Replication activated
1/29/2024, 12:42:47 PM->↑0 (31) ↓10 (LIVE)
1/29/2024, 12:42:47 PM->Replication completed
1/29/2024, 12:42:47 PM->STORAGE <- DB (modify,plain) 02 Private Notes/General/Test sync.md
1/29/2024, 12:42:47 PM->Processing 02 Private Notes/General/Test sync.md (02 Priva:10-4f) 
1/29/2024, 12:42:49 PM->Processing configurations done
1/29/2024, 12:42:49 PM->All files enumerated
1/29/2024, 12:43:01 PM->Content saved:02 Private Notes/General/Test sync.md ,chunks: 3 (new:2, skip:2, cache:1)
1/29/2024, 12:43:01 PM->STORAGE -> DB (plain) 02 Private Notes/General/Test sync.md

The last line here seems where it's stuck, the ⏳ symbol remains. This time, a single restart of obsidian resolves it - on the side that did the change. The side that is pulling doesn't have the issue.

Maybe related:

Since the last update there also seem a big amount of weird logs where it seems to compare linux timestamps maybe? It seems to go through almost the entire vault it seems

1/29/2024, 12:45:51 PM->STORAGE <- DB :ZZ Archive/XXX1.md
1/29/2024, 12:45:51 PM->1699829328 < 1706475568
1/29/2024, 12:45:51 PM->STORAGE <- DB :ZZ Archive/XXX2.md
1/29/2024, 12:45:51 PM->1699829328 < 1706475568
1/29/2024, 12:45:51 PM->STORAGE <- DB :ZZ Archive/XXX3.md
1/29/2024, 12:45:51 PM->1699829328 < 1706475568
1/29/2024, 12:45:51 PM->STORAGE <- DB :ZZ Archive/XXX4.md
1/29/2024, 12:45:51 PM->1699829328 < 1706475568
1/29/2024, 12:45:51 PM->STORAGE <- DB :ZZ Archive/XXX5.md
1/29/2024, 12:45:51 PM->1699829328 < 1706475568

Thank you for your hard work!

from obsidian-livesync.

It looks like 0.22.4 has stabilized the situation so far!

I'll continue to observe for a moment but otherwise we may be able to close this soon. Thank you!

from obsidian-livesync.

It is a great relief to hear that!
I would love to thank you once again for your patience and cooperation!

from obsidian-livesync.

Ok, after a few hours and 4 clients of real world usage, it seems to be fixed :) Thank you! I'll close the issue

from obsidian-livesync.