-
Notifications
You must be signed in to change notification settings - Fork 153
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
Ruby LSP indexing fails with undefined method required_positionals
#2630
Comments
required_positionals
I see the same issue |
Same here. Using zed editor. |
Same here: |
It seems like indexing broke with today's release of version 3.6.0 of |
Thank you for the bug report! This PR should fix this #2631. |
We've released the fix in v0.18.4. To update, follow the steps here: |
Thank you @vinistock and @andyw8 ! Forcing up to v0.18.4 with this command from the docs fixed it for me:
|
Dependabot does not do this because it resolves with Ruby 3.0 from the gemspec and tapioca now only supports 3.1 This unblocks prism 1.0 which is required for the ruby-lsp to update to the latest version. Currently it runs into Shopify/ruby-lsp#2630, causing a restart loop. To make sure this does the right thing on older rubies, I added a step to print the resolved lockfile on CI
Dependabot does not do this because it resolves with Ruby 3.0 from the gemspec and tapioca now only supports 3.1 This unblocks prism 1.0 which is required for the ruby-lsp to update to the latest version. Currently it runs into Shopify/ruby-lsp#2630, causing a restart loop. To make sure this does the right thing on older rubies, I added a step to print the resolved lockfile on CI
Description
Ruby LSP Information
Ruby LSP Information
VS Code Version
1.93.1
Ruby LSP Extension Version
0.8.1
Ruby LSP Server Version
0.18.3
Ruby LSP Addons
Ruby Version
3.3.5
Ruby Version Manager
asdf
Installed Extensions
Click to expand
Ruby LSP Settings
Click to expand
Workspace
User
Reproduction steps
rubocop
Code snippet or error message
I have tried in different Rails projects and I have the same behavior.
In an older Rails project running ruby 3.0.4, I get the following error:
The text was updated successfully, but these errors were encountered: