Skip to content

ruby_lsp fails to install bundled gems if the project Gemfile uses a relative path for the gem. #3227

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

Open
therealjasonkenney opened this issue Feb 21, 2025 · 2 comments
Labels
bug Something isn't working help-wanted Extra attention is needed non-vscode Stale

Comments

@therealjasonkenney
Copy link

therealjasonkenney commented Feb 21, 2025

Description

Reproduction steps

  1. I was using ruby 3.1 at this time. (via asdf) asdf local ruby 3.1.2
  2. I was using this project: Ameelio Canvas LMS
  3. Run gem install ruby-lsp
  4. Run bundle install
  5. Try ruby-lsp
  6. See unexpected behavior: bundler-multilock, due to Bundler::Plugin::MalformattedPlugin (plugins.rb
    was not found in the plugin.)`

I currently have a workaround cd .ruby-lsp; ln -s ../vendor vendor

@therealjasonkenney therealjasonkenney added bug Something isn't working help-wanted Extra attention is needed non-vscode labels Feb 21, 2025
@vinistock
Copy link
Member

Thanks for the issue. Can you provide an example of what type of relative path in the Gemfile reproduces the issue?

Also, it seems to have some relationship with the BUNDLE_PATH. What do you have configured for Bundler and at what level (user or project setings)?

Copy link
Contributor

This issue is being marked as stale because there was no activity in the last 2 months

@github-actions github-actions bot added the Stale label May 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help-wanted Extra attention is needed non-vscode Stale
Projects
None yet
Development

No branches or pull requests

2 participants