-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: switching between neovim stable|nightly errors with "cannot load incompatible bytecode" #225
Comments
I can not reproduce this. I've added Was the 0.8.1 version linked to puc instead of jit maybe? If so you should now get an errro instead that you need to have a neovim version built with luajit |
Still getting the same exact error unfortuntaely. Neovim 0.8.1 version output:
Neovim nightly:
Which fails with error:
|
Your LuaJit version is exactly the same between both. Is there anything else special about your installation? Where did you get the 0.8.1 from? Is that also appimage? |
My 0.8.1 comes from the void linux packages (prebuilt binaries), I will download the 0.8.1 appimage, clean and reinstall lazy and see if that makes any difference. |
Ok, so I downloaded the 0.8.1 appimage, deleted the
|
You need to delete |
Oops I guess I missed that, so switching between the I can workaround this by doing a simple test (in the code) and deleting |
I just pushed a change that should fix the incompatible byte code as well |
Can you see if the new version works without issues? |
Just tested, worked like a charm :-) Tyvm! |
Did you check docs and existing issues?
Neovim version (nvim -v)
0.8.1
Operating system/version
Linux
Describe the bug
When cache is enabled trying to use the nightly appimage results in the error:
Steps To Reproduce
curl -LO https://github.com/neovim/neovim/releases/download/nightly/nvim.appimage
chmod a+x nvim.appimage && nvim.appimage
Expected Behavior
Auto-detect the compiled bytes are a from different neovim version and regenerate cache when switching between stable and nightly.
The text was updated successfully, but these errors were encountered: