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

Live Share: sharing REPL port doesn't work #803

Closed
svdo opened this issue Oct 2, 2020 · 4 comments
Closed

Live Share: sharing REPL port doesn't work #803

svdo opened this issue Oct 2, 2020 · 4 comments
Labels
bug Something isn't working connect

Comments

@svdo
Copy link
Contributor

svdo commented Oct 2, 2020

I'm using VSCode/Calva with Live Share a lot. According to the docs, you can share local network sockets over Live Share as well. We try to use this for Calva's REPL, so that the guest can also evaluate Clojure code in the host's REPL. When the guest tries to connect to this socket, using “connect to a running REPL”, I would expect to have to provide a port number, which doesn’t happen. Instead, in the VSCode “Log (Window)“, I see this error:

[2020-10-01 13:58:17.820] [renderer1] [error] Error: EROFS: read-only file system, mkdir '/.calva': Unknown (FileSystemError) (FileSystemError): Error: EROFS: read-only file system, mkdir '/.calva'
    at _handleError (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:706:514)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:94:5)

It seems like Calva doesn't detect that this folder is already present on the host. Please note that if .calva is in .gitignore, which it normally is of course, on the guest I don't even see the .calva folder and output.calva-repl buffer, so I guess the mechanism needs to take this into account.

@bpringe bpringe added bug Something isn't working connect labels Oct 2, 2020
@svdo
Copy link
Contributor Author

svdo commented Oct 3, 2020

I think it's probably because jackin.ts is using fs instead of vscode.workspace.fs, see also https://code.visualstudio.com/updates/v1_37#_vscodeworkspacefs. I'll try to verify this weekend and hopefully make a PR.

@PEZ
Copy link
Collaborator

PEZ commented Oct 3, 2020

jack-in.ts shouldn't be involved in a connect scenario, but we could have factored something wrong, of course.

In any case, the usage of fs could very well be the problem. We have tried to fix such usages, but there are probably a few of them still there.

@svdo
Copy link
Contributor Author

svdo commented Oct 4, 2020

Ok that's good to know. Conceptually, what I'm trying to accomplish, that should be using the command "Connect to a running REPL server in your project", right? (As opposed to the non-project one)

@svdo
Copy link
Contributor Author

svdo commented Oct 17, 2020

This has been released in 2.0.127.

@svdo svdo closed this as completed Oct 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working connect
Projects
None yet
Development

No branches or pull requests

3 participants