Closed thepenguinthatwants closed 1 year ago
I made some changes to the lua-loader in lazy.nvim, and forgot to make the relevant changes in LazyVim. Just fixed it there.
Will make a new release in a bit
@folke It looks like this issue might not be fully solved. I have just faced this issue with AstroNvim when adding community repos, and discussed it in their discord channel.
The maintainers of AstroNvim have tested it out and concluded that there exists a bug somewhere in the lazy.nvim
cache_loader stuff. I have no idea how to come with a minimum reproducible for this bug, so I am literally linking it to the relevant issue in the AstroNvim repo: https://github.com/AstroNvim/astrocommunity/issues/206, and the relevant lines from the chat log/transcript on their discord discussion here: https://discord.com/channels/939594913560031363/942007419050029086/1108413031643349073
Apologies upfront that I couldn't hone the bug report into a minimal example.
Sorry for the comment above, I believe this is a different issue probably and only related because the cache_loader
is having some issues. I have opened an appropriate issue #803
Did you check docs and existing issues?
Neovim version (nvim -v)
NVIM v0.8.3
Operating system/version
arch linux
Describe the bug
Steps To Reproduce
Updated plugins and saw this issue. Doesn't seem to be caused by other plugins etc.
Expected Behavior
Being clean without this error. I can be fine when restoring to earlier lazy-lock.json state and using restore.
Repro