-
-
Notifications
You must be signed in to change notification settings - Fork 181
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
Corruption during sync process breaks plugin files locally and in remote DB #553
Comments
Within 30 seconds of finishing writing the initial bug report, I finally decided to actually look inside the vault files in .obsidian, and voila, It looks like around half the files in .obsidian were left encrypted at some point, for example: ./plugins/homepage/manifest.json:
ewoJImlkIjogImhvbWVwYWdlIiwKCSJuYW1lIjogIkhvbWVwYWdlIiwKCSJ2ZXJzaW9uIjogIjQuMC43IiwKCSJtaW5BcHBWZXJz[...]
./plugins/better-word-count/main.js:
J3VzZSBzdHJpY3QnOwoKdmFyIG9ic2lkaWFuID0gcmVxdWlyZSgnb2JzaWRpYW4nKTsKdmFyIHN0YXRlID0gcmVxdWlyZSgnQGNv[...]
./plugins/obsidian-raindrop-highlights/main.js:
LyoKVEhJUyBJUyBBIEdFTkVSQVRFRC9CVU5ETEVEIEZJTEUgQlkgRVNCVUlMRAppZiB5b3Ugd2FudCB0byB2aWV3IHRoZSBzb3Vy It seems likely that the direct cause had to do with interrupting LiveSync at the wrong time, probably by quitting Obsidian. I don't really know how the decryption process is handled though. Some (uninformed) ideas on how to address this:
Let me know if there's a straightforward way to decrypt these files? If so I might just keep the setting on and fix it if it breaks. Otherwise I'll disable encryption and rebuild the vault, and should be smooth sailing from there on. editThose could potentially be from compression rather than encryption? edit 2Never mind, I hadn't enabled compression at any point |
Thank you for opening this issue! And so sorry for this! It seems that the files had been decrypted successfully. However, it had not been decoded as a binary files. |
EDIT: solved (partially)
It turns out that there was a failure to decrypt some of the .obsidian files. I will leave more details in a comment.
Abstract
Some (but not all) plugins are failing to load on start. The plugin folders appear intact in the filesystem, but not within the app.
I'm not 100% certain that LiveSync did cause this issue; It's very possible that this was totally my own error or another plugin caused it. However, it happened at the same time that I was messing with various LiveSync settings, and I hadn't made any real changes to other plugins or Obsidian in the several hours before the issue happened.
Expected behavior
Actually happened
Reproducing procedure
I have no idea what caused it, but I'll provide environment details below. The issue is persistent.
Report materials
Went over the length limit...
report-data.txt
Screenshots
Server config check:
Other information, insights and intuition.
Obsidian plugins
In GUI
The plugins shown in the Community Plugins GUI in Obsidian:
In JSON
The plugins listed in .obsidian/community-plugins.json:
In local filesystem
The content of .obsidian/plugins/:
Potential causes
Attempts to fix
While LiveSync seems to have caused the problem initially, the problem seems persistent in the vault contents, probably
Other observations
[]
insyncIgnoreRegEx: \.DS_Store|[]|^raindrop\/
in livesync-configThe end
I do have backups and nothing was lost in this case thankfully!
Thanks so much for your hard work on this plugin; It's certainly the best open source option for Obsidian syncing I've seen, and I'd be interested in contributing once I get it all figured out.
EDIT: Solved partially
See comment below
The text was updated successfully, but these errors were encountered: