Slight weirdness with jack-in version stuff. Deets in 🧵
At startup I see:
Effective nREPL dependency versions:
nrepl: 1.5.2 (configured in settings)
cider-nrepl: 0.58.0 (Calva defaults)
cider/piggieback: 0.6.1 (Calva defaults)
Latest available nREPL dependency versions found on Clojars:
nrepl: 1.5.1
cider-nrepl: 0.58.0
cider/piggieback: 0.6.1
Note that Calva thinks nrepl 1.5.1 is the latest on Clojars, but 1.5.2 is available and I have that configured in settings.@pez Am I misunderstanding what Calva should be doing here?
Could it be cached?
Cached where?
I updated my settings to 1.5.2 as soon as that was released -- but it's been available for ages at this point and Calva is still saying 1.5.1.
"ages" = "a week ago"
How/when does Calva check Clojars for new versions?
It should do that when Calva starts. Have you restarted Calva the last week?
It should be checking using that command you cooked up. Don’t recall right now. I do note that it says 1.5.1 for me too, so something is probably broken.
Yeah, I've restarted Calva multiple times since then (mostly just reload window but also a few VS Code restarts, and even a couple of full Windows reboots 🙂 )
I don't remember the command we thought we'd agreed on... it was something with find-versions?
> clojure -X:deps find-versions :lib nrepl/nrepl :n 1
{:mvn/version "1.5.2"}See if we log anything in the developer tools that can be a clue.
Not really sure where to look or what to look for but in the Window log after reload there's this:
2026-01-06 17:17:27.296 [info] [Window] Started local extension host with pid 45000.
2026-01-06 17:17:27.914 [error] [Window] Extension 'betterthantomorrow.calva-backseat-driver CANNOT USE these API proposals 'extensionRuntime'. You MUST start in extension development mode or use the --enable-proposed-api command line flag
2026-01-06 17:17:27.915 [error] [Window] Extension 'betterthantomorrow.calva-power-tools CANNOT USE these API proposals 'extensionRuntime'. You MUST start in extension development mode or use the --enable-proposed-api command line flag
2026-01-06 17:17:27.915 [error] [Window] Extension 'ms-vsliveshare.vsliveshare' wants API proposal 'notebookCellExecutionState' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
🙂And this for Calva itself (this error appears for a number of extensions at startup):
2026-01-06 17:17:36.291 [error] [Window] navigator is now a global in nodejs, please see for additional info on this error.: PendingMigrationError: navigator is now a global in nodejs, please see for additional info on this error. The extensionRuntime is needed in development for the ClojureScript REPL to work on the Calva code. We pay with a warning in prod. 😃
Anywhere specific you'd like me to look for debugging hints?
If we don’t even log anything to the console, I think that may also indicate that there is something fundamentally wrong… Please file an issue. Then whoever takes on the issue can look for debug hints.
I don't understand where you want me to look for output/logs tho'...
What do you mean by "the console"?
I’m sorry. You showed me some logs you had found and afaict they are from the console (the Developer Tools console) so I thought you had found it. 😃
I don't know how to view the Developer Tools console...
Those were from the Window log...
These are the available logs from Developer: Open log...
Ah. You find Developer Tools in the Help menu.
Heh, and I have it full screen so the Help menu isn't visible. Okay, I see this in Developer console:
[Extension Host] Latest deps.clj.jar version: v1.12.4.1582
console.ts:139 [Extension Host] deps.clj.jar is up to date
console.ts:139 [Extension Host] [Calva] Jack-in dependency versions already populated in global storage: {nrepl: '1.5.1', cider-nrepl: '0.58.0', cider/piggieback: '0.6.1'}And here's the Calva START/END stuff:
[Extension Host] Calva activate START
console.ts:139 [Extension Host] deps.edn launcher check, executing: 'clojure --version' ...
console.ts:139 [Extension Host] activation: 0.005ms Joyride activate START
console.ts:139 [Extension Host] Joyride Eval LM Tool registered successfully
console.ts:139 [Extension Host] joyride_request_human_input LM Tool registered successfully
console.ts:139 [Extension Host] Joyride LM Tools registered successfully
console.ts:139 [Extension Host] activation: 3.977ms Joyride activate END
console.ts:139 [Extension Host] activation: 4.195ms
console.ts:139 [Extension Host] deps.edn launcher check - 'clojure --version' - stdout: Clojure CLI version 1.12.4.1582
console.ts:139 [Extension Host] deps.edn launcher check - 'clojure --version' - stderr:
console.ts:139 [Extension Host] deps.edn launcher check: 'clojure --version' command works, using 'clojure'
console.ts:139 [Extension Host] clojure version: 1.12.4.1582
log.ts:440 INFO Extension host (Remote) is unresponsive.
log.ts:440 INFO Extension host (Remote) is responsive.
console.ts:139 [Extension Host] vscode-redhat-telemetry 0.8.1 (redhat.vscode-yaml): Updating vscode-redhat-telemetry configuration from
console.ts:139 [Extension Host] Current deps.clj.jar version: v1.12.4.1582
console.ts:139 [Extension Host] Issue #2071: languageConfiguration {onEnterRules: Array(0)}
console.ts:139 [Extension Host] Issue #2071: formatOnType? true
console.ts:139 [Extension Host] Issue #2071: newIndentEngine? true
console.ts:139 [Extension Host] Backing up existing clojure-lsp to /home/sean/.vscode-server/extensions/betterthantomorrow.calva-2.0.543/backup/clojure-lsp
console.ts:139 [Extension Host] Downloading clojure-lsp from
console.ts:139 [Extension Host] Calva activate END I'll paste this into the ticket above...
Thanks. Doesn’t look like we have any logging on the check.
What and where is that "global storage"? Maybe if I remove that it'll recalculate the latest? Although based on the PR that implemented this, it looks like it should do all three fetches (current stored values, latest values, settings values)