-
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
uninitialized constant SyntaxTree::BraceBlock #2346
Comments
@tvdeyen The logs indicate a very old version of To help troubleshoot, can you try temporarily add the latest version in your |
(please re-open if you need further assistance) |
@andyw8 I have not installed Since you asked, I now did anyway and it bundled correctly, so there seem to be no Bundler related issues. I started VSCode and it says it now uses the latest version (0.17.8). I then removed the gem from the It then shows this in the logs:
Now it is a different error. I then tried with Ruby 3.3.4 and that works. Maybe a Ruby 3.3.3 issue? |
You're still running on the extremely old v0.0.3
As Andy mentioned, something in your bundle is locking the If you have the If you don't, try to update the gem and check why that's failing. BUNDLE_GEMFILE=.ruby-lsp/Gemfile bundle update ruby-lsp If that command does not upgrade it to v0.17.8, then the project may be constraining one of the Ruby LSP's runtime dependencies, which are
|
@vinistock that actually worked 🎉
Since I do not have My guess is Ruby 3.3.3 (that has issues with installing correct gems, no?) |
Anyhow it works for me now, but maybe worth adding to the TROUBLESHOOTING section or making sure the extension updates the |
It does try to update the gem on boot, not sure what was failing there. Better than surfacing this in TROUBLESHOOTING, I would love if we could warn users that we attempted to upgrade, but that didn't work. Maybe Bundler can inform us that's the case? |
I also had this problem and I just wiped my |
There's no detriment to removing the |
Description
Reproduction steps
This error message appears
The text was updated successfully, but these errors were encountered: