Skip to content
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 Language Server Crashes in Remote SSH Environment #153

Closed
abrookins opened this issue May 5, 2019 · 11 comments · Fixed by rubyide/vscode-ruby#480
Closed

Ruby Language Server Crashes in Remote SSH Environment #153

abrookins opened this issue May 5, 2019 · 11 comments · Fixed by rubyide/vscode-ruby#480
Assignees

Comments

@abrookins
Copy link

abrookins commented May 5, 2019

  • VSCode Version: 1.34.0-insider (user setup)
  • Local OS Version: Windows 10 1809, build 17763.379
  • Remote OS Version: Linux - RHEL, uname -r: 3.10.0-957.10.1.el7.x86_64
  • Remote Extension/Connection Type: SSH

Steps to Reproduce:

  1. Install vscode-ruby extension in VS Code on Windows from the Extensions menu
  2. Set up a Ruby project on a Linux (RHEL) server/VM
  3. Connect to Linux server from within VS Code on Windows using "Remote-SSH: Connect to host..."
  4. Open a Ruby file hosted on the remote server within VS Code on Windows in the window currently connected to the remote server

Expected
The file opens without any error messages. Language server features work.

Actual
An error appears in the "Output" pane at the bottom of the screen and language server features do not work.

[Info  - 09:56:26] Initializing Ruby language server...
[Info  - 09:56:26] Rebuilding tree-sitter for local Electron version
[Info  - 09:56:26] Rebuild succeeded!
/home/andrew/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/node: symbol lookup error: /home/andrew/.vscode-remote/extensions/rebornix.ruby-0.22.3/server/node_modules/tree-sitter/build/Release/tree_sitter_runtime_binding.node: undefined symbol: _ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorE
[Error - 09:56:26] Connection to server got closed. Server will not be restarted

Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: No

@benjaminwood
Copy link

This also happens when "Developing inside a Container": https://code.visualstudio.com/docs/remote/containers

@Chuxel
Copy link
Member

Chuxel commented May 7, 2019

@rebornix
Copy link
Member

rebornix commented May 7, 2019

Yes it is. I'm waiting for reviews for tree-sitter-ruby.

@rebornix
Copy link
Member

rebornix commented May 9, 2019

For the ruby ls crashing issue, I already sent out PR for both tree-sitter-ruby and vscode-ruby

Will ping once we have them merged and released.

@wingrunr21
Copy link

Hi all,

I'll do the work in vscode-ruby this weekend to get the PR there merged and a release cut

@Chuxel
Copy link
Member

Chuxel commented May 30, 2019

@wingrunr21 @rebornix Looks like this is fixed correct? If so we can close.

@Chuxel
Copy link
Member

Chuxel commented Sep 6, 2019

Closing - looks like this was fixed a while ago.

@Chuxel Chuxel closed this as completed Sep 6, 2019
@OmriSama
Copy link

Idk if this was really fixed, the vscode-ruby extension still doesn't work properly on Remote and it's been super frustrating.

@Chuxel
Copy link
Member

Chuxel commented Sep 18, 2019

@OmriSama The change referenced here was merged, but there may be a new issue.
I see rubyide/vscode-ruby#533 was raised recently. I'd track progress there since it likely is an extension issue given the scenario.

//cc: @rebornix

@wingrunr21
Copy link

@OmriSama

The next release is bringing full support. I’m sorry you are frustrated, but the extension has never stated it had full support for remote. There are tracking issues and milestone 0.26.0 for the full support.

@OmriSama
Copy link

@wingrunr21 awesome! Looking forward to it

@vscodebot vscodebot bot locked and limited conversation to collaborators Oct 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants