-
Notifications
You must be signed in to change notification settings - Fork 172
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
Server Initialization failing #1725
Comments
Thank you for the bug report! I'm seeing the same types of errors on some projects for the This error is thrown by bundler itself before we get into any LSP code. When we boot the server using There's a little bit more context here rubygems/rubygems#6667. FWIW, Bundler itself gives two options: update bundler or update the default gem. Updating bundler didn't do anything for me, but updating |
Actually, scratch that. I think #1125 will fix this. |
Awesome thanks @vinistock, I'll keep an eye out for the release with that PR! Really appreciate y'all being so responsive |
Talked to @paracycle and @k0kubun and here's a bit more context. This issue is indeed related to rubygems itself. It requires default gems, such as uri, which may cause a conflict with applications that also require The long term solution, would be to have rubygems vendor the default gems that it needs to function, so that it does not impact applications that also depend on those same gems. #1125 won't actually fix this. Even if the default gems are added as runtime dependencies, there could still be discrepancies between the version required by rubygems and the version locked by the application. I believe the only workaround is to indeed update the default gem to the version that gets required by rubygems itself, so that we can avoid a conflict. |
Operating System
MacOS 13.6
Ruby version
3.14
Project has a bundle
Ruby version manager being used
chruby
Description
I'm opening vscode from my terminal using
code .
. In the past we've had to do this in order to get our Gemfile recognized properly for this project. Checking the logs for Ruby LSP there isn't anything that stands out to me as a quick fix:The text was updated successfully, but these errors were encountered: