Closed jake-duchesne closed 2 weeks ago
Hi @jake-duchesne
Which version manager are you using?
Also, could you try create a separate project using Ruby 3.3 to see if the error happens there?
This does not seem like an issue with the Ruby LSP. It seems gem installations ended up getting into a bad state.
If you run gem install prism
, does that succeed? If not, you may want to delete your existing gem installations and then re-install.
The incompatible library issue typically happens when you installed a native extension (like Prism) in one Ruby version and then you're trying to use that installation in a different one.
For example, if you installed the gem and it had its extensions compiled for Ruby 3.1, you cannot reuse the same installation for Ruby 3.2 and that would lead to the error you're seeing.
Hi @jake-duchesne
Which version manager are you using?
Also, could you try create a separate project using Ruby 3.3 to see if the error happens there?
Hi @andyw8, asdf on the version manager and 0.16.6 is working on other projects, so it seems Vinicious is right here - apologies for the misaligned issue. I'll try to figure it out, I'm not super familiar with how gem installations work with extension compilations but gem install prism
does work.
Anyways, thanks for the explainer and apologies again.
Description
Reproduction steps
Other information leading to this and attempted fixes:
bundle install
within the.ruby-lsp/
folder and regenerated theGemfile.lock
thererm -rf .ruby-lsp/
and restart VSCode/ExtensionCode snippet or error message
I've gone through about all the troubleshooting that I can think of or that I've read from the docs, please let me know if I can provide any more useful information.