Launching a jack-in silently fails in all projects after upgrade to 2.0.233, even after downgrading

[TuggyNE]

Today, after I upgraded Calva to the latest release, I can't start the project REPL for any of several projects that were just running fine in 2.0.231. Unfortunately, this appears to have somehow corrupted some configuration, since downgrading to 2.0.231 is no good anymore either. There is no error message and nothing appears to happen at all. If I copy the jack-in command using the command palette, I can start the REPL server just fine, but attempting to connect to it with Calva also silently and immediately fails. Reloading the VS Code window or restarting VS Code as a whole changes nothing. Where would I find a log file for this kind of problem? There appears to be nothing in /var/log, /tmp, or /var/tmp on this Mac.

[bpringe]

Are there any potential clues in the developer console after this issue occurs? (Help -> Toggle Developer Tools -> Console tab)

[bpringe]

Also, what gets printed in the output window?

[bpringe]

Jack-in seems to work fine for me in a deps.edn project and a shadow-cljs project. What type of project(s) are you experiencing this with?

[TuggyNE]

There was nothing at all in the output window or the clojure-lsp connection log, or any other log file I could find, and no jack-in process ever started to display anything in the terminal either. (/Users/ntuggy/Library/Application Support/Code/logs/20220107T183339/* had various repetitions of the same stuff seen in the respective VS Code windows.)

Unfortunately, I didn't think to check the developer console, and I just finished restarting the whole Mac a few minutes ago, which apparently makes the problem unreproducible. Sorry about the poor timing on that.

The projects all use Leiningen, no CLJS, little or no REPL customization.

[bpringe]

Well, I'm glad the issue seems to be gone after the restart! Let us know if you experience it again.

[TuggyNE]

Just ran into this again. Had a working REPL using 2.0.459 or so (although I now doubt that the versions are important), updated Calva without restarting, and opened a new project window with 2.0.467. This new project was unable to connect a REPL even after restarting extensions and even VS Code. (And after restart, the old project was also unable to connect.)

Affected project types: standard Leiningen (x2), somewhat customized shadow-cljs.
Developer console, Calva says, Calva Connection Log, and nREPL messages (after enabling with Toggle nREPL Logging) all show nothing at all relevant.
It's especially annoying since it seems to fail so early in the process.

[TuggyNE]

It may be worth noting that trying to connect to a running lein repl server with .nrepl-port file populated also silently fails immediately after selecting "Leiningen" project type from Connect to Running REPL Server in Project. (Still not much in any logs or console. But I did notice an unrelated problem, #2605.)