Closed Seunggu0305 closed 8 months ago
Reopening...
Ah, I am not the only one that this happened to. I have been sketching my head for the last 2 hours. I would like to know if it's related to a recent update. This morning, I updated .NET as well as the VMWare Workstation. After that, I discovered that Obsidian Git was giving this same error. To diagnose, I opened WSL2 and found it was now broken, stating it could not locate the Hyper-V network bridge. I finally fixed all of that, and I can confirm that Git works as it always has. Within WSL2, I can use Git, and within CMD.exe, I can use Git.
The Obsidian Git plugin hasn't been updated in 2 months, so I suspect the .NET or the VMWare Workstation update broke it. That is just my theory...
I will keep poking around because this problem is affecting my work. I will update if I figure out how to resolve it.
@Seunggu0305 I found the cause on my end. The obsidian-local-images-plus plugin pushed an update that somehow broke Obsidian Git's usage of the Buffer module (actually, it is simple-git). I don't know how or why. I noticed that if I moved my Obsidian vault to another drive (from my secondary drive D to my desktop on C), I could open my vault and Obsidian Git worked. if I moved it back to D, it broke.
As it turned out, Local Images Plus was to blame. I reverted back to Local Images Plus 0.15.8 and that fixed the issue.
From what I can tell, the Local Images Plus plugin in 0.15.8 overrides the global Buffer.isBuffer
method, which affects simple-git
within Obsidian Git.
@absane Thanks for your fast check and reply. How did you revert back the Local Image Plus to 0.15.8?
@absane Thanks for your fast check and reply. How did you revert back the Local Image Plus to 0.15.8?
So you had that installed as well and currently at 0.15.9?
I had a backup of my previous plug-ins, so it was as simple as drag and drop. But their release section on their GitHub repo has it as well.
I opened an issue there as well, letting them know of the breaking change.
@absane @Seunggu0305 I have just made some temporary fix and updated latest release. Just reinstall the plugin.
@absane @Sergei-Korneev Thanks for your help!
To be clear, steps I took to resolve:
Thanks to OP and co for research, updates, and speed resolution
Describe the bug
my local Windows 10 laptop's obsidian git says it is not ready with the above notice.
how can I fix this?
Relevant errors (if available) from notifications or console (
CTRL+SHIFT+I
)Steps to reproduce
I have no idea with steps
Expected Behavior
No response
Addition context
No response
Operating system
Windows
Installation Method
None
Plugin version
2.22.0