-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Load error! (Cannot read property 'map' of undefined) #1042
Comments
Does refresh (CTRL-R) get rid of this problem? Could you open the console (CTRL-SHIFT-I) and copy and paste here errors you see there? Thanks. |
I tried CTRL-R it doesn't help, still the same. I also tried "Find and Fix Consistency Issues" and I thought it fixed, but after I reopen trilium the issue is still the same. I also tried to delete this recovered file, but I am not able to delete them. Also, I replied already to your comment in this thread: |
@projectrk thank you, the screenshot suggests that the error originates on the backend. Could you please post here content of backend log (or send it to zadam.apps@gmail.com)? You can open the backend log from Global menu on top right -> Show backend log. Thank you! |
08:26:18.470 INFO Generated sourceId=sifNespgaGL5 |
Hello, thank you for providing the backend log. Unfortunately it looks like the document database is corrupted, but not in the application logic sense, but really on the database/file/OS level. Was something untypical happening with the document file? I imagine that for example trying to sync it with Dropbox while the application is running could corrupt the file. Anyway it seems the database is corrupted in the way that the database is readable, but not writable so data can be recoverable. For SQLite this means that the database needs to be rebuilt. In 0.42.4 I added the possibility to backup document file now: This executes So I recommend clicking on that, and copying |
yes, I was using MEGAsync to sync it. I used the symlink "ln -s" to sync it to my MEGAsync folder. Is there any other way to sync it properly without corrupting? What I did, is to wait for MEGAsync to finish synching and thats the time I will shutdown my linux. |
Recommended way to sync is documented here - https://github.com/zadam/trilium/wiki/Synchronization To be able to use generic syncing tools you must guarantee that there no two processes writing to the DB at the same time - so when MEGAsync is doing the sync, Trilium must be stopped. IMHO it's all way too fragile, one time you forget and you have a corrupted file. |
Hi,
Greetings. I got this error in one of my content in trilium note. Please help what to do with this.
Trilium Version 0.42.3
OS: Ubuntu 20.04 LTS x64
Dell 7559 Inspiron
Thank you in advance
The text was updated successfully, but these errors were encountered: