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

Failed to connect to the remote extension host server when using Cursor Fork #86

Open
ashkan-leo opened this issue Nov 4, 2024 · 7 comments

Comments

@ashkan-leo
Copy link

Hi folks,

When connecting with VS Code Version: 1.93.1 I get the error

Failed to connect to the remote extension host server (Error: WrappedError(WrappedError { message: "error checking server integrity", original: "failed to run command \"/home/ashkan/.vscode-server/cli/servers/Stable-38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40.staging/server/bin/code-server --version\" (code 127): Could not start dynamically linked executable: /home/ashkan/.vscode-server/cli/servers/Stable-38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40.staging/server/node\nNixOS cannot run dynamically linked executables intended for generic\nlinux environments out of the box. For more information, see:\nhttps://nix.dev/permalink/stub-ld\n" }))

My configursion is:

services.vscode-server.enable = true;
services.vscode-server.enableFHS = true;

Any advise on how to fix?

@Ten0
Copy link
Collaborator

Ten0 commented Nov 4, 2024

VS Code Version: 1.93.1

This seems like a relatively old version. Are you sure that's the correct version number, and if so, have you tried removing the .vscode-server folder, then restarting the user service ?
Also, does it work without FHS?

@ashkan-leo
Copy link
Author

Thanks for the quick reply. You are right. Updating VS Code and deleting the .vscode-server folder fixed the issue. 👍

A side note: using Cursor (a fork of VS Code) the problem persists. Here is the cursor version

Version: 0.42.4
VSCode Version: 1.93.1
Commit: b1e87884330fc271d5eb589e368c35f14e76dec0
Date: 2024-10-29T17:17:29.347Z
Electron: 30.4.0
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.0.0

@Ten0
Copy link
Collaborator

Ten0 commented Nov 4, 2024

It might be that it stores lts data in another folder than .vscode-server, in which case that has to be specified in the corresponding option of the module IIRC, and that might work but I'm not sure.

@ashkan-leo
Copy link
Author

Do you know how to figure out where it stores the data?
But if it is storing it somewhere else, then how come it is producing this error? Failed to connect to the remote extension host server (Error: WrappedError(WrappedError { message: "error checking server integrity", original: "failed to run command \"/home/ashkan/.cursor-server/cli/servers/Stable-b1e87884330fc271d5eb589e368c35f14e76dec0.staging/server/bin/cursor-server --version\" (code 127): Could not start dynamically linked executable: /home/ashkan/.cursor-server/cli/servers/Stable-b1e87884330fc271d5eb589e368c35f14e76dec0.staging/server/node\nNixOS cannot run dynamically linked executables intended for generic\nlinux environments out of the box. For more information, see:\nhttps://nix.dev/permalink/stub-ld\n" }))

@ashkan-leo ashkan-leo changed the title Failed to connect to the remote extension host server Failed to connect to the remote extension host server when using Cursor Fork Nov 5, 2024
@Ten0
Copy link
Collaborator

Ten0 commented Nov 5, 2024

That's the error you get from not patching.
The path is in the error: $HOME/.cursor-server

@ashkan-leo
Copy link
Author

Ah you're right. I got confused.
Is it possible to have this installed in both the vscode-server and cursor-sever directories?
I did try to copy over all the files in vscode-server to cursor-server but that did not help and is resulting in the same error.

@Ten0
Copy link
Collaborator

Ten0 commented Nov 7, 2024

No it's not supported at the moment.
I would be willing to merge a PR adding support for taking both a path and a list of paths as path option if that doesn't increase the code complexity too much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants