Git crash when looking for updates of this plugin via lazy

[kmoschcau]

When I recently tried to check for updates of this plugin via lazy, git crashes on the first attempt, then fails on a second attempt because of a lock file that has not been cleaned up. The lock file in question is .git/objects/info/commit-graphs/commit-graph-chain.lock

My hunch is, this is because of the branch named windows-😐.

I've had this happen on both Windows and Linux, both running git version 2.43.0. The only place where it didn't happen was in WSL, where git is of version 2.34.1.

Here is the related Lazy issue: folke/lazy.nvim#1204

[L3MON4D3]

Oh okay.. I'd be a bit surprised if it was caused by a branch-name, but I'll delete it just in case, it's old anyway.
Was it a one-time ocurrence, or could you reproduce it?

[kmoschcau]

I can repro it each time I check for a new version. It's a single button press.

[L3MON4D3]

I've deleted the branch in question, does it still occur?

[kmoschcau]

I just checked again on the Windows machine and it does still occur. Even after completely fresh checkout. The initial clone, including submodule works. Just checking for updates fails. I'll have a look later on the Linux machine.

[ZeekDaGeek]

I know this really isn't a satisfying solution, it doesn't help you prevent it from happening again, but:

Placing your cursor over LuaSnip and pressing x to delete, then pressing I (capital i) to install again solved the problem.

So basically, have you tried turning it off and on again?

EDIT: I'm sorry I think my error might actually be more related to #1071 then this one, I should have looked harder, sorry.

[kmoschcau]

@ZeekDaGeek I did that already and that does allow updating. Though my problem is that I'd have to do that every time just to check for updates.
@L3MON4D3 I realize I didn't get back to you, the issue is still present on the Linux machine as well. Though at this point I think this is more of an issue in Lazy than with LuaSnip. LuaSnip is just the only plugin (I think) that uses submodules in my plugin list. So seems to me this is something that Lazy does when checking submodules, that broke in newer Git versions.

[ghost]

For whatever its worth, this is happening to me as well.

[veejaypee]

reinstalling the plugin with x I on lazy fixed this.

[kmoschcau]

reinstalling the plugin with x I on lazy fixed this.

As already stated before it allows you to do the update once, but it does not fix the underlying issue of the check for updates failing.

[kmoschcau]

Ultimately we found a workaround in the lazy thread: folke/lazy.nvim#1204 (comment)

I tested it myself and it prevents the error from occurring. Closing this.