Open chadkennedyonline opened 2 years ago
I've also seen this on a straight Windows installation, using scoop Clojure. No WSL involved.
IF the issue is with starting up nREPL, I loaded a previous version of the extension and it worked for me I have WSL2 setup , java installed, VSCODE on windows 11 with remote WSL extension running.
@denizoz There was a related change in 2.0.330. Can you tell us if the problem persists for you in this version?
Can you also test this, @chadkennedyonline?
I don't know if that would fix the issue, but it's worth checking it out.
Steps to reproduce
1) VS Code running under Windows 10. 2) Follow instructions at https://calva.io/wsl/ 3) Run
Calva: Fire up the "Getting Started" REPL
.Expected
"Initializing Clojure language features via clojure-lsp" spins for a limited time in the status bar.
Actual
"Initializing Clojure language features via clojure-lsp" spins forever in the status bar.
Additional Information:
In the Clojure Language Client window I see:
After turning on verbose logging, the beginning of the log in the Clojure Language Client window shows this:
Specifically, note that
rootUri
is null. This link may be demonstrating a similar issue from a different project: https://github.com/eclipse/xtext-core/issues/57Trying using
clojure-lsp.bat
didn't help - same error.Workaround
After running
Calva: Fire up the "Getting Started" REPL
, close the cljs files in vscode, then open the temp folder where they were located in vscode. Now run "Calva: Fire up the "Getting Started" REPL again, but tell it to use the existing temp folder.Credits
Thanks to @bringe, @PEZ, and especially to @ericdallo for helping me to work through the issue. Eric was super-helpful!