No idea. That sounds very strange. Does it work with other Clojure projects?

Yes, a normal Clojure project can't evaluate 😞

I meant: yes it fails for even normal clojure projects.

@U039K02M4UB Is this similar to what you had?

It might be that the VS Code install is corrupted. To test that is a bit of a bother, but you can test if things work with a fresh install of VS Code Insiders: https://code.visualstudio.com/insiders/

sounds good, thank you for the help!

For the record: it worked!. Thanks!

You are welcome. So then either your VS Code installation is corrupt, or you have some extension that messes things up. The latter is unlikely, But if you could see if an extension bisect gives anything.

Sometimes a restart of the computer helps... ¯\(ツ)/¯

I checked the Shortcuts and Jupyter notebook had the same shortcut, but it was uninstalled some time ago. So, maybe some hanging config?

yes, very strange but I think something among those lines might have been the problem.

This version breaks clojure-lsp auto starting in VSCode for me. Going back to version 2.0.328 fixes this for me.

Not good! Can you describe your workspace layout some?

Sure, I have the below folders. where . is the main source and docs-code contains a project somewhere in a subfolder. It doesn't matter if I remove both extra folders and only have the main folder in my code-workspace file, clojure-lsp says it isnt started and I should choose a project.

"folders": [
		{
			"path": "."
		},
		{
			"path": "..\\_docs-code"
		},
		{
			"path": "..\\bootstrap\\bootstrap-4.1.3"
		}
	]

Going back one version from 239 to 238 makes clojure-lsp auto start.

Here's a screenshot with the folders removed

If I then click the project and click start clojure-lsp starts

It just won't auto start

hovering the mouse over clojure-lsp gives a popup 'Open a clojure file to see the server status'

When 328 autostarts it, which project-root is it using? You can see this with the command for showing serverinfo.

let met check

"project-root-uri": "file:///d:/thier/Documents/GoogleDrive-Thorax/Dev/aorta-develop",

the one it should use

the code-workspace file I opened is in that folder

So that's . in that file? (I'm not using workspace folders myself much.)

yes, thats the default path

Can you screenshot the explorer view too? Maybe that makes it clearer to me why that's the project where it should autostart.

Sure

And please file an issue about this.

I will file an issue, having lunch atm 🙂

Smaklig spis

tak

^ Swedish ^ for something like Enjoy your meal. But I don't think there's a general expressions like that in English. It would be more like Enjoy your lunch... Well, I am not a native speaker so probably am missing some idiom. 😃

<!subteam^S03BGSAUPTQ>, @m401. I'm not pulling the rollback lever here just yet. Let me know if you think I should. Thinking that most users do not use workspaces and that starting clojure-lsp manually is OK while we fix it. I am keen on trying to reproduce the error with the new e2e testing infra that I just put in place.

@U0ETXRFEW I know, my stepmother is Swedish 😁

In Dutch we have eetsmakelijk

That sounds very much like it matches the Swedish idiom.

Indeed it does. Eet is from eten which is like eat from eating and smakelijk is the exact same word as Smaklig

We also say Smakelijk eten wich is an exact translation to Smaklig spis

Is smakelijk completely missing from English?

Google says Tasty, but there doesnt seem a direct translation from ours to

Nah, that is more how something tastes/that it tastes good/has a lot of flavour.

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

Please add your findings/screenshots etc to that issue, @thierry572.

will do, on it

@U0ETXRFEW What do you mean by VS Code Workspace proper ?

I mean as opposed to a plain folder.

Haha, I didn't realize it was you who had filed that issue, @thierry572 😃

:face_with_hand_over_mouth:

Updated my reply and the op.

🙏

Thanks for the report. @thierry572 can you check the developer tools console to see if there are maybe any relevant errors being logged when you load vscode?

What exactly do you want me to look for? all console message point to workbench.desktop.main

this is on 239

Hmm I don't think that's related. My guess is you would be getting that same output for 238

Ok I will be trying to reproduce and fix later today.

this comes after it. let me check 238

I’m struggling to reproduce this issue. I guess this has something to do with it being on Windows..? I’m not sure how to go about fixing this as I do not have access to a Windows machine if that’s the case.

@U0ETXRFEW any ideas?

anything I can do, test, code, fix, whatever?

Imho I think it has to do with the differences in path handling between linux and windows?

I’m afk. Can you assist @thierry572 to the code option , @m401 ? 😍

Happy to but I’m also strapped for time atm - currently in the US for meetings so organising a common time might be tricky. @thierry572 would you be free in a couple hours or tomorrow (your) morning for a pair-programming session?

Completely missed your message there @m401 going to bed now, have to work in the morning.

Ok will see if I can get access to a Windows machine later in the week to test

Let me know if you want some company, @m401. 😃

@thierry572 When you get a chance, can you try this vsix build and let me know if it fixes the issue for you: https://output.circle-artifacts.com/output/job/09bad264-3d9f-4a5a-9c44-28107379a6e4/artifacts/0/tmp/artifacts/calva-2.0.330-pull-2060-33b8c7e3.vsix

will do

Dunno if I did this right, but I copied the contents from the zip/extension folder into the c:\Users\thier\.vscode\extensions\betterthantomorrow.calva-2.0.328\ folder and started VSCode.

Tadaa

Starts and works

All in its glorious self

lsp popup looks nice n sorted too

Kondo started and giving response in the Problems tab

> Dunno if I did this right Well, no 😃 You should have used the meatballs menu in the VS Code Extensions pane and selected Install from VSIX (can also be done from command line, but anyway).

The meatballs menu, new one for me :melting_face:

Your way obviously worked. But I think VS Code can get pretty confused about it.

let me try the correct way

I'm a Swede, meatballs everywhere. ¯\(ツ)/¯

made a backup of the contents before starting ofcourse

right, my browser saved the vsix as zip, thats why

anyway, installed from vsix and same outcome

Calva is utilizing cider-nrepl and clojure-lsp to create this VS Code experience.

well ill be damned this quote thing

im going to bed

thanks for fixing @m401!

Thanks for being quick to test and confirm, @thierry572!

you're welcome @U0ETXRFEW,now im really going to sleep

Cool! Glad this worked. Love me some 1 liner fixes

In that case, @U0ETXRFEW here is the PR: https://github.com/BetterThanTomorrow/calva/pull/2060 :)

Haha thanks for helping me set the machine up! :)

Especially since later in the log it seems that it should create the deps.clj version file just fine, and then you should not see the above log on subsequent starts of Calva...

I use lein indeed

on 238 it does the same\

238 start

238 end

239 start

239 end

Lots of problems there!. It says it fails to download clojure-lsp too. I don't think any of this is new, btw. Might be Windows issues, none of us in the <!subteam^S03BGSAUPTQ> use Windows...

I have no issues on 238 tho, nor before 238

The clojure-lsp error seems extra Windows specific. It says it is a download error, but I think it is the chmod that goes wrong. And then, probably, the chmod is not needed, so you have no issues. But the universe knows that something went wrong, so we need to get it fixed.

Its always the damn universe

Have the same issue on Windows, but it goes so far That nothing works even navigating with Ctrl arrow or selecting forms. It only See this error and on the bottom left it always says activating extension.

When you say "Windows" -- @thierry572 and @UD8TU3HP0 -- are you talking about native Windows with Powershell/cmd and your Clojure files all local? (i.e., not WSL2) (I ask because I'm not seeing any issues on Windows/WSL2 -- but in that setup, VS Code installs Calva into the Linux side so "everything" operates there, except for the UI... the files are all on WSL2 as well)

Yes, native Windows

For me yes nativ had only Problems with wsl2

2 different systems

'k... @UD8TU3HP0 Curious about your WSL2 problems but we can follow up on that in a separate thread if you want? I've been using that setup with Calva for ages and loving it.

Its more a Problem with what and how we develop nothing specific to Calva

@UD8TU3HP0 Calva never activates for you?

Well it does but wehn i start the lsp for one Project something happens end then everything is kind of broken and shortcuts dont work

This is with 329? Or even with 328?

No only with 329, 328 works just fine My guess something with the multi-project lsp and Windows mess something up

Please add whatever details you think are relevant to this issue, @UD8TU3HP0 https://github.com/BetterThanTomorrow/calva/issues/2054 If you can describe the workspace layout and project structure that would be great. If it's Workspaces involved, or just plain folders.

And of course, if you can try debug it in development mode, that would be awesome.

Will Do this tomorrow I guess i can spare 1h or so to check this out 👍

I was wondering if the new sorting of project choice might have anything to do with it? Or does that not apply to clojure-lsp? Since in 239 the popups to choose a project to start lsp for are not sorted like described in the release commits. In fact the main project is not even at the top in my screenshots?

My guess it that those two issues has the same cause. Good clue!

Yea there must be some difference with how paths are represented/formatted/something on windows which would affect all of these things.

Yes That is also my guess, i added my findings to the Ticket also