Open mattpenner opened 9 months ago
Hi! Thanks for the report, and for the details. I can't say I understand what's going on, but it all looks eerly similar to this issue reported earlier today/yesterday:
Though, there we saw kubernetes and docker being involved somehow. But can you check if you have the WSL extension enabled and, if so, if it makes a difference disabling it?
Thanks @PEZ , I saw that issue as well. I do not have the WSL loaded and could find no mention of it in my extensions. Unless this is now happening under the hood I do not see that this is involved.
I also just disabled all of my extensions other than CALVA: Clojure & ClojureScript Interactive Programming and Calva Spritz. However, even after reloading VSC I still get the same result. I also tried to run VSC as Administrator, and had the same output.
The output errors are pretty slim. Any other ideas of where I could pull more verbose error logs from?
It could be that the error message gets lost because it's being directed to the repl client which disconnects on the error. Pure speculation here, but you could try to disable Calva: Redirect Server Output To Repl
And see if you get a trace in the jack-in terminal.
Which version of Java are you using?
@PEZ Thanks for the quick and responsive replies. ☺️
I get the following Java version info:
openjdk version "17.0.8.1" 2023-08-24
OpenJDK Runtime Environment Temurin-17.0.8.1+1 (build 17.0.8.1+1)
OpenJDK 64-Bit Server VM Temurin-17.0.8.1+1 (build 17.0.8.1+1, mixed mode, sharing)
I unchecked the Redirect Server Out to Repl setting you mentioned, but after reloading there was no change. No additional info is in the Terminal or Output screens. 😕
Thanks! From the messages we do get it seems the error occurs in the nrepl server. Maybe there's a way to get it to be more verbose... There are also a newer version of nrepl than Calva is using by default. There's a slim chance it could work by configuring Calva to use it (1.1.0-alpha1
).
I started to suspect that there's some kind of problem in the combination of OS and VS Code version. So I tried to connect on a Windows box I have access to with an older version of VS Code (1.77 something, I forgot to take a note) and upgraded to latest (1.82.2, like you have). Unfortunately (well...) I could still connect. I'm not sure what version of Windows I am using, I'm a Windows noob...)
You could try see if it might be a VS Code version thing by using an older version. There are versions here: https://github.com/ewanharris/vscode-versions I think 1.81.1 might be of interest, seeing how the Electron and Node has been bumped after that. I would do this test if I could reproduce the problem, but so far I can't.
I am getting this same error too with 2.0.392. Not using VSCode but Flatpak VSCodium on Pop!_OS:
Version: 1.83.1 Release: 23285 Commit: 36d13de33ac0d6c684f10f99cff352e2f58228b3 Date: 2023-10-12T18:26:29.496Z Electron: 25.8.4 ElectronBuildId: undefined Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: 11.4.183.29-electron.0 OS: Linux x64 6.5.6-76060506-generic
Just to be more thorough, you can also check the developer console (Help -> Toggle Developer Tools -> Console tab) for errors, as well as enable the logs between the nrepl server and client and check those. Since it does seem like the nrepl server is at least starting, you might see some helpful info in those nrepl logs.
I am starting to learn Clojure on Windows 10 and just installed the Calva VS-Code extension. Upon trying to run the Calva: Fire up the Getting Started REPL files I get the following error in the Terminal:
The out.calva-repl window states:
The VS-Code output screen shows:
I don't see any other errors, error codes, etc.
Just before this I installed Java via adoptium and installed Leiningen via https://ericnormand.me/guide/how-to-install-clojure#windows and restarted.
The Clojure Lein REPL works just fine in the command line.
I am using VS-Code 1.82.2 on Win10 10.0.19045. I do have several VS-Code extensions running for other projects I work on (PowerShell, Angular, Android, etc.).
I have tried starting VS-Code as an administrator, ran the Getting Started overwriting the temp downloaded files or using them, restarted VS-Code several times, and restarted my laptop. Can't seem to get this to work with my current knowledge.