https://www.dendron.so/ logo
Join Discord
Powered by
VSCodium often becomes unusably slow, like it hang...
# chat
c
VSCodium often becomes unusably slow, like it hangs for multiple seconds. I've never seen this in VSCode (where I don't use dendron), so I assume it has to be dendron related. Is there anything I can do to improve performance? Or any steps to debug? Somebody mentioned the extension bisect option before, but by now I'm pretty sure that dendron is the issue. It seems like dendron "hangs" the whole editor. I read something about that in the server package. Are there any experimental performance optimisations I could try?
s
Hi, could you share more about the files being deleted? Sync doesn't do any destructive operations, the worst is does is 
git pull --rebase
c
Yeah, what kind of info can I share?
I posted an issue, so happy to discuss there if that's easier.
It might be that the repo was loaded for the first time on my second computer, and in that case, somehow the second computer created an empty vault and when doing a 
git pull
managed to overwrite the current contents with its new empty vault?
s
Hmm, I wonder if workspace initialization cloned but didn't pull the vault. Then Sync could have added and committed something weird like what you described, then 
pull --rebase
might have thought that the new commit intended to delete everything. Still very weird, but perhaps pull shouldn't rebase but merge instead.
I'm working on the sync right now, so I'll see if I can reproduce what happened.
c
Yeah, it could be that. I've just posted a similar idea to the issue.
Happy to do a screenshare and show you the commits, etc if you like.
It happened a few days ago and my biggest fear is that I didn't notice!
Okay, yeah, that's what happened. I did a quick test. I'll post a reproduction now.
s
Oh, thanks for testing it out! I'll make sure this is promptly fixed.
c
Glad we got to the bottom of it, now I can relax that my data is safe! 🙂
5 Views
PreviousNext
Powered by