Build failed?

[caiomcg]

Build failed?

[BrendanVadacoraBell]

Updating to neovim 0.10.0 fixed this issue for me.

[caiomcg]

Can confirm that updating to 0.10.0 fixes the issue.

NVIM v0.10.0
Build type: Release
LuaJIT 2.1.1713484068

Thank you @BrendanVadacoraBell !!

[Conni2461]

Maybe checkout #597 (comment)

We didnt change anything. I am the only maintainer right now and i dont have time to invest time in this project right now. And in the past past two months. Hopefully that changes next month :)

[shinspiegel]

Would you mind sharing the Lua version?
Looks like there is an issue with the Lua 5.1 which is a dependency for some internal stuff.
My best guess at this moment,

Also, you can use the flag to enable the debug: https://github.com/nvim-lua/plenary.nvim?tab=readme-ov-file#troubleshooting

[caiomcg]

Would you mind sharing the Lua version?

Of course, this is what I have installed:

NVIM v0.9.5
Build type: Release
LuaJIT 2.1.1703358377

Not sure how do I get the actual Lua version. Is this enough? Wil try to enable debug as well.

[shinspiegel]

Not sure how do I get the actual Lua version. Is this enough? Wil try to enable debug as well.

lua --version I guess,
Or lua -v... Something like that should do the trick.

[caiomcg]

Got it!

:lua print(_VERSION)

I do have Lua 5.1 installed, it came packed with Neovim as I don't recalled manually installing Lua on my machine

Edit: It is the same version that I have on MacOS. Maybe this is a Lazy.nvim issue?

[jesses-code-adventures]

I am also getting this on nvim 0.9.5 on MacOS (I'm on 14.3.1) using Lazy.nvim

[numine777]

This issue seems to have reappeared in neovim nightly, just a heads up

NVIM v0.11.0-nightly+185b227
Build type: Release
LuaJIT 2.1.1713773202
Run "nvim -V1 -v" for more info

Lua version in neovim shows 5.1

[numine777]

To be fair, my installation of neovim is through nix, so this may just be a me issue. Refactoring to handle plugins through nix solved this (although I had enjoyed keeping lazy so that my config was portable to non-nix machines, but yet another me problem).

Definitely not worth spending lots of time on the issue if it's just me, but figured I'd put it out there in case anyone else has the same issue. Thank you for taking the time to respond so quickly!