-
Notifications
You must be signed in to change notification settings - Fork 130
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
Default Activation Not Installing ruby-lsp Gem #1764
Comments
Thank you for the bug report! I'm not sure what the issue here is, but here are some suggestions to try out:
If neither works, I suspect it could be related to VS Code permissions. The LSP might be failing to create the Some users were discussing this #1586. If you discover it is indeed a permission issue, please let us know which permission exactly you denied to VS Code. Full disk permission is definitely not needed (as I didn't grant that and can use the LSP just fine), so we've been unable to figure out exactly what causes the issue. |
Thanks for the response. Asdf is up to date (v0.14.0), and after updating Bundler to the latest version (2.5.6), I'm still getting the same response as above. I'll look into the permissions and let you know if anything ends up working. |
This issue is being marked as stale because there was no activity in the last 2 months |
Operating System
Ubuntu 20.04.5 LTS (WSL2)
Ruby version
3.1.2
Project has a bundle
Ruby version manager being used
asdf
Description
When I install the vscode extension, the Ruby LSP server crashes with the following information in the output tab:
When I install the ruby-lsp gem globally to try to avoid the error (which I know is not how I'm supposed to be installing it), I then get the following errors when I launch vscode:
Finally, when I try to start the server by running ruby-lsp, I get the same "command not found" message if I have not installed the ruby-lsp gem globally, but once I install it globally myself, starting the server by running ruby-lsp works, just not in vscode.
The text was updated successfully, but these errors were encountered: