I was just about to post about this, but wanted to try something first. Basically, I came here to see if it had been reported, saw there was a new version today, and reinstalled the prior version and everything was working again. I was just updating back to the new one to verify, and sure enough, clojure-lsp is not initializing. Also, lots of calva keybinds don't work at all, and trying to use them gets a brief "Activating Extensions..." item on the status bar. Meanwhile, clojure-lsp still has a wait spinner and vscode continues to consume CPU. Going back one version seems to fix it though.

@U4LCNMMGS can you file an issue from vscode? The Help menu has an entry for this. It will pass along some system info that could be of help figuring out what went wrong. And please describe the kind of project you are using. Could be something with how it’s structured.

Sure, it'll be a little later this morning. The kind of project is ... chaotic? lol I'll include info though.

We have a repro-project now, @U4LCNMMGS And we have rolled back the change, v2.0.334 should work exactly as 332 did.

It does, but I saw it was a rollback, and missed you had a repro, so I was about to do that. Thanks for letting me know!

One additional data point I was going to include, and I'll drop it here in case it's useful: While lsp not initializing is the main thing, it wasn't the first thing I noticed, and maybe this will provide a useful clue: The first thing I noticed was that a lot of calva keybinds stopped working. The whole key stopped working though, as though the calva keybind was selected, but then didn't fire. It wasn't all of them, but delete, backspace, ctl-shift-right, pretty much anything related to paredit that I tried.

Thanks! Sounds like something crashes…

@U4LCNMMGS @U04RCKSF91N Can you two try this vsix build (https://output.circle-artifacts.com/output/job/63f952f1-c9f9-47a6-920d-87697bc2d33f/artifacts/0/tmp/artifacts/calva-2.0.335-pull-2090-3a17fa8f.vsix) and let me know if the issue is resolved for you (and/or if you find any other issues?). I would very much appreciate it!

Sorry, no, no change from 333. clojure-lsp does not initialize and paredit keybinds are dead keys.

OK I think I figured it out this time. Can you try this one: https://output.circle-artifacts.com/output/job/a27c59c3-799b-442f-8546-911ccbe78162/artifacts/0/tmp/artifacts/calva-2.0.335-pull-2090-af1761b7.vsix 🙏

turns out an older version of the extension works, so I guess something went wrong with the update?

Hi! Can you try with an earlier version of Calva and see if it that works? In the extensions pane you can hover the Calva entry and you should get a settings button or something that brings up a menu.

Ah. How much older did you try?

I'm using v2.0.331

Can you test with 332? Or was it 332 that caused you problems?

Hi @U04RDFU3PJ4 are you running into this issue on Windows? If not, which OS are you using?

I see that keeping Shift+Alt keys pressed down and either doing Up Arrow or Down Arrow adds the above or below text lines to the selection, which is usually good enough.

Shift+ctrl+alt+left/right is what you are looking for, I think.

Those one's move parens around. I'm just looking to expand the selection but only in one direction. There wasn't a perfect way of doing this in IntelliJ either. The good enough trick is good enough.

Oh, sorry. was not at a computer. Skip the ctrl key there.

The Calva select commands are listed and demoed here: https://calva.io/paredit/#selecting

I got it now. If you start at the right place then Shift+ctrl+left will grab upwards and Shift+ctrl+right will grab downwards. And you can back step by going in the opposite direction. I think you were giving me Mac keys but I'm on Linux 🙂.

## Change Took offered "update to latest" on Calva extension, from within VScode, i.e. offered automated update from: v2.0.332 to: v2.0.333 Accepted "restart VS code" option. Update seemed to succeed as far as VScode concerned.

## Fault/result - unable to use REPL or see documentation - errant behaviour when clicking greyed out "REPL" (VScode bottom ribbon) to connect repl, - never successfully connected to repl - sometimes offered usual options (leiningen, figwheel, etc), - sometimes seems to attempt to start REPL without asking for these - never offered normal option when clicking on REPL (VScode bottom ribbon) to disconnect from the repl - same options from the VScode command menu also did not work

### Further info/indicators The problem was encountered on both leiningen and deps.edn projects, all of which had no problems with REPL yesterday. - "clojure-lsp" spinning wheel when in clojure project (VScode bottom ribbon), - never changes from spinning wheel status - left it in this status for several minutes with no change - "activating extension" spinning wheel frequently appears for 1-2 seconds in VScode bottom ribbon, when try to e.g. "Manage Clojure LSP servers" - hover over to get documentation on clojure functions etc simply provides "Loading...." - it seems to start JVM processes in project folder (checked with jps -m in terminal)

## Attempted fixes (none worked) - uninstalling and disabling Calva extension from VScode - killing VScode and opening again - killing JVM processes combined with above in different orders - complete restart of PC

# Successful fix Reverting calva extension to v2.0.332 This removed all issues.

# Environment information ## OS: M/soft windows pro 10, latest, more info with VScode info ## VScode info: Version: 1.75.1 (user setup) Commit: 441438abd1ac652551dbe4d408dfcec8a499b8bf Date: 2023-02-08T21:32:34.589Z Electron: 19.1.9 Chromium: 102.0.5005.194 Node.js: 16.14.2 V8: 10.2.154.23-electron.0 OS: Windows_NT x64 10.0.19045 Sandboxed: No ## (clojure-version) "1.10.1"

Thanks! Please sync with @U02CX2V8PJN about creating an issue on GitHub. It would be extra great if you can share a project where this is reproducible.

@U0ETXRFEW you can use this and just open it as folder with 2.0.333 and the same issue happens https://github.com/LouDnl/at-at

@U04R3PP70P3 You can add your findings in the this issue, they are exactly what I'm experiencing 🙂 https://github.com/BetterThanTomorrow/calva/issues/2087

Thanks both: info added as comment in your ticket as requested

Yes, issue, please. 🙏

https://github.com/BetterThanTomorrow/calva/issues/2087

334 is up. Can you test?

reloading

different issue, it takes a while for calva to start. same erroneous oiutput

ill post the õutput to the git issue

https://github.com/BetterThanTomorrow/calva/issues/2087#issuecomment-1439983108

I copy pasted the complete devtools console output from start

It takes a while, but eventually it starts

but these errors are not there in 332

the ones relating to Calva

ill post the 332 log aswell

That's very strange... I must check what I put into 334 now.

it does work tho

let me quickly check the 332 logs

posted them in the issue, definitely less issues and it starts quicker

@U0ETXRFEW see dm

@U02CX2V8PJN Can you perhaps give this vsix a try: https://output.circle-artifacts.com/output/job/63f952f1-c9f9-47a6-920d-87697bc2d33f/artifacts/0/tmp/artifacts/calva-2.0.335-pull-2090-3a17fa8f.vsix I think this should fix the issue for Windows users but need some more testers.

I will

Installed, will report

It starts, lsp starts, no errors in console, I jacked-in, got REPL but then it (being Calva and lsp) just stops being responsive. Can't use backspace in REPL, won't evaluate, lsp keeps loading and when clicking the loading icon it shows activating extensions next to it. Now the console has this message: INFO UNRESPONSIVE extension host: starting to profile NOW log.ts:398 WARN UNRESPONSIVE extension host: 'betterthantomorrow.calva' took 57.724388663300765% of 2887.793ms, saved PROFILE here: 'file:///c%3A/Users/thier/AppData/Local/Temp/exthost-942fab.cpuprofile'

And the cpu profile doesn't seem to have anything worth noting

but if you want it, let me know

Hmm interesting. Does this hang happen deterministically? Does it happen when you only have the LSP server running and no REPL connection?

Notice anything in particular that triggers it?

I was able to reproduce this actually. Debugging!

nice!

🙏

Please give this one a try @U02CX2V8PJN https://output.circle-artifacts.com/output/job/a27c59c3-799b-442f-8546-911ccbe78162/artifacts/0/tmp/artifacts/calva-2.0.335-pull-2090-af1761b7.vsix 🙏

will do

We're a step closer, everything starts. Waited a while and noticed that nothing happens when I click on the clojure-lsp name in the bottom status bar (blue one). I can jack in, that works and the repl responds aswell

There are however errors in the console

Weird. Havent been able to reproduce this one

Does the lsp features work though?

It says ”scheme contains illegal characters”, but could it still be some spaces or non-ascii characters in the project path that @U02CX2V8PJN has, but not you @U04HKE0BTC5?

dont think theres spaces in there? am i overlooking something?

ill check if lsp works as soon as i can

I reproduced it! It happens when clicking on the management menu while there is a .lsp/config.edn file. Probably something to do with the .. Will get a fix out soonest.

Thats good news! I have indeed got a .lsp/config.edn and a .clj-kondo/config.edn and both contain a line with folders to exclude.

Ok the issue was our usage of Uri.parse which was interpreting the leading C:\ on windows as a URI scheme. Please try out this vsix: https://output.circle-artifacts.com/output/job/c5f196bd-001a-4960-af33-e98b5c601376/artifacts/0/tmp/artifacts/calva-2.0.335-pull-2090-5877356d.vsix Hopefully that’s the last of them!

Will do, just woke up

Installed, reloading

No issue so far, lsp starting up, no console errors. will jack-in when lsp is done

still starting

let me try and see whats going on by setting the logging to verbose

oof, trying to restart lsp throws a bunch of errors

ill reload the window

oh, the errors are cut in half, sorry bout that

No problem. What's important here is to try figure out if this is new since 333 or 335.

still starting after reloading window, ill try and jack in to see what happens then. the clojure language client output shows nothing strange

If it's something introduced earlier, it is better we handle it in a separate issue+PR.

Try delete the .lsp/.cache directory and see if it could be some bad state there causing the start to fail.

okat

okay

jack in works

Those errors being thrown is ‘normal’ when trying to stop a client that is still starting and existed prior to 333

okay, hadnt noticed them before.

deleted the cache folder and restarted vscode

How long does it usually take to start?

throws this in console

quite fast actually, let me time it on the previous version

I guess it is a problem with spaces in that path there.

No, I was sloppy reading the message. Disregard that ^ 😃

What is even throwing that.. that doesn’t seem related to the work in 333/335

hmm, let me try to see whats goung on here as lsp is still loading even on 334, which is weird as it worked just fine yesterday.

Ok, then I think the issue you have now is some bad state unrelated (probably) to these recent changes

I hope at least :P

I'm hoping and thinking the same. 😃

can i enable kondo logs somewhere?

last time it took this long it was kondo throwing a tantrum, but i only saw that after installing and enabling the kondo extension as standalone

Can you try with regular VS Code. If it is your Insiders install that has accrued some bad state...

just did, have tried both now. nothing strange in the console. I removed the workspace storage and cache for lsp and kondo

going to try another project now

to see if thats the issue here

I was about to suggest a computer reboot. But much better to check with another project first. 😃

yea its something to do with the project or the project settings

my at-at fork works fine

ill try the new vsix on the at-at fork

vsix works fine now

il go over my project settings

And maybe try the problematic project with clojure-lsp only. If that's possible. Not sure how to do that....

Ping @UKFSJSM38

okay, so I copied config.edn from both kondo and lsp to my at-at fork and everything still works

with the new vsic

vsix*

Here: https://clojure-lsp.io/troubleshooting/#server-is-not-initializing

will try

btw, this error is strange as the file does exist. spaces in path maybe?

The clojure-lsp executable that Calva uses lives in its extension folder. VS Code has a command Extensions: Open Extensions Folder that will show you where the various Calva versions live.

the exe file starts fine

I think it's busy doing something

ill wait a bit longer

Finally, it started

it's doing something that makes it take up 7gb of ram. I have a running issue at lsp for this, it was solved. something must have changed. ill dive into this myself

yeah, fixed it. I had large files in my project that are normally excluded but werent now somehow

@U04HKE0BTC5 your vsix works

restarting vscode now to clear some cache and see if there are any errors in console still, maybe unrelated to this

Once this is released, I'd like an issue for each error message you have in that console, @U02CX2V8PJN. I think I got rid of a few of them a while back, but we should go for Zero. Will make it so much easier to debug things.

yeah sure

like these? they appear after jackin

dont see anything going on that should throw this tho

Since you even ask about it, yes, like these. 😃

right, will wait for release and then throw some issues at you :melting_face::rolling_on_the_floor_laughing:

I think those particular ones are not Windows specific, but anyway. It would be super helpful!