RFC: Synchronization problems in 0.63

[zadam]

Describe feature

Hello, since 0.61 there has been a lot of trouble / bugs with the synchronization. I fixed all the problems I could find / identify and it looks like it did help for some people, but others still seem to be having problems.

I'd like to get this working for everybody, but for that I need help from those who encounter problems. Here's what I need to diagnose / debug the problem:

• I need an anonymized database from both client and server. You can anonymize the database in Options -> Advanced.  You can find them in the anonymized-db subdirectory of the "data directory" which can be seen in the "About Trilium Notes".
• I need both client and server logs. You can find the log subdirectory of the "data directory" which can be seen in the "About Trilium Notes". Please include the logs for the whole days, not just excerpts showing the errors.

ZIP these files and send them to [email protected]. Thank you!

Additional Information

No response

[rom1dep]

@zadam is this what's holding back 0.63?

[zadam]

Yes, I'd like to get the sync finally sorted out. The other thing is that 0.63 contains only minor improvements, so there's not much pressure to release.

[justyns]

FWIW I was having a lot of sync issues after upgrading, however I haven't experienced any in the recent weeks. I think what finally worked for me was making a backup of my trilium db, deleting the db files from all of my clients, importing the db into a single client and then start syncing from scratch.

[perfectra1n]

Sent an email, that includes the information you requested above! Hopefully it helps :)

One thing of interesting to note - I didn't have this issue with my Trilium client (whose data and therefore DB has existed for >6 months), but I've reimaged my workstation this week. After restoring my Trilium client's data from the server (after the workstation reimage), this issue popped up after ~48 hours. Not sure if it's related at all, but it's a coincidence I at least wanted to mention.

Edit: yep, I can confirm that what I said above is true - when starting a client from scratch on v0.62.6 and then restoring server (v0.62.6) data, this bug happens. However, when using my trilium-data folder from whichever version of Trilium was current at the time of 11/03/2023 (v0.61.11 ?), syncing to the server (v0.62.6) works just fine. You might find this interesting @zadam, I can also email you the "working" anonymized DB as well, if you think that it would help.