Okay the command is displayed so I can run it at the command line and see the stack trace that way. This was the command:

chris@fedora:~/code/restaurant$ clojure -Sdeps '{:deps {nrepl/nrepl {:mvn/version,"1.1.1"},cider/cider-nrepl {:mvn/version,"0.47.1"}}}' -M:dev -m nrepl.cmdline --middleware "[cider.nrepl/cider-middleware]"

Exception in thread "main" Syntax error compiling at (contrib/js_interop.cljc:27:3).

Caused by: java.lang.RuntimeException: No such namespace: js

you should be able to look at either the output or the jack-in terminal for errors in the jack-in procedure

Yeah should have been printed to the jack-in window at least.

this is probably because there is a user.clj file on the classpath. When repls don't start, commenting out that file and then loading it explicitly should also show the errors

Here’s a build of Calva that makes the Jack-in a bit more visible, also when the jack-in terminal is not revealed. • https://output.circle-artifacts.com/output/job/37687eda-9c09-44bc-99b8-a5a7bb9c2cc5/artifacts/0/tmp/artifacts/calva-2.0.464-2597-more-visible-jack-in-errors-b25e2194.vsix @U0D5RN0S1 it would be great if you could test it, reverting whatever you did to fix the problem, and see if you think this would have helped you better. To install this build, use the Install from VSIX… option from the top meatballs menu in the Extensions pane. (You probably will have to rename the package downloaded from .zip to .vsix.) Anyone else who’d like to take this version for a spin? It would be great! 🙏

I replicated the hanging then installed the .vsix. I jacked-in again and this time after a while got an unclear stack trace dialog. But after pressing "Show Jack-in Terminal" I got what I got from running outside the IDE. Excellent 😄🎉

> an unclear stack trace dialog Would you prefer the error message is less verbose?

FYI: The information was there all the time. What we help with in this build is to find it.

Yeah I was just thinking about how verbose the error message was. I think the user just needs to know that there's a stack trace and press the button to see it. Too many indecipherable stack traces in the Java (and esp Clojure) worlds. But what you have now is pretty good, just it is a bit pointless to be trying (badly) to show a stack trace when there's a nicely formatted version of it a button press away.

Yes I worked that out (the stack trace was there all the time). Just it was 'hidden' to me at the time.

Gotcha. I’ll stop including the error message with that dialog. Thanks!