The behaviour with auto-creation of an ns form for new files does not happen for me. Anyone else having the same or better luck?

Hm, it works fine for me, whenever the editor is connected to nREPL or not, an ns form is created for any kind of clojure files.

@pez as I understand you don’t see an ns form at all, right?

Exactly. It behaves just like old boring Calva. 😃

Just re-installed the extension and it still works. How do you create a new file?

Hello! I have a problem running Calva with the Remote Extensions pack, when it is installed into the remote server. Namely connecting to a running repl does not work, even the dialog asking for host/port does not come up. When I click the nREPL at the status bar, it reads > Cannot read property '0' of undefined Any tips? Update: It has nothing to do with Remote, it seems. When I open a new VS Code window and run Calva: Connect to Running..., I get the same issue. Having v2.0.133 Trying the second similar command I get > Command 'Calva: Connect to a Running REPL Server, not in Project' resulted in an error (Cannot read property 'toString' of undefined)

That does not sound good at all. Can you try with an earlier version of Calva and see if this is a regression we've introduced? Can't really see when we would have introduced that though, but we introduced support for LiveShare in v2.0.127, so try 126, maybe?

how do I downgrade? And can I see detailed logs of the error somewhere?

126 seems ok

The developer console might show something.

with 126 I get the connection type selection window and can click eg. "Generic" but then nothing more happens. I expect to be asked for a port.

We've changed the behaviour of that generic project type. I can't right now remember how it used to behave. But, sure, it should prompt for a host and a port.

What about version 130?

Will try. 126 has this in dev console, among other related logs: > stack trace: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undefined at validateString (internal/validators.js:112:11) at Object.join (path.js:1039:7) at m (/Users/holyjak/.vscode/extensions/betterthantomorrow.calva-2.0.126/out/extension.js:1:44790)

That's mostly old hat, we've quite completely changed the implementation since 126.

Ok. But 126 does not work either, presumably due to ☝️, since it does not really connect, though it gets further than 130. I have tried 130 but it also fails with "Cannot read property 'toString' of undefined"

What does your project look like? lein/deps/something else?

fixed - after restarting VS Code, v130 is working

Interesting. What about 133?

Will try when 130 is done. Currently it is still at ; Hooking up nREPL sessions... while trying to connect to localhost:1234 while lein repl :connect 1234 worked fine

It should not be hanging there for very long...

Please file an issue using VS Code's issue reporter. It will send along info about your system and such that might help in tracking the problem down.

FYI 133 is still failing with "Cannot read property 'toString' of undefined" even though I restarted VS Code after the upgrade https://github.com/BetterThanTomorrow/calva/issues/853

I can reproduce it.

Or, I could a short while. Now it works again... Very strange.

Can you try with v132?

Just tried to reproduce it, and failed. Works fine for me, v133.

I had this strange thing where I got 130 working once but cannot anymore so it seems to be somehwat random

Indeed. But a bit random in how the bad is distributed too. I had one failure, and now I can't reproduce it for the life of me...

Ok, on 130 I got the error, then run jack in (just to test), closed, then I succeeded connecting to the server partially (stuck at ; Hooking up nREPL sessions... again)

If you have the time, you are welcome to try track this down in the debugger, @holyjak.

What kind of server is it you are connecting to?

My bad, I stopped the ssh tunnel so the repl indeed could not be reached anymore 😅

Haha

Now the ns form is created as it should too, btw, @zelark. Seems something needed to be cleaned out, that got cleaned out when I reloaded VS Code to try some old versions.

But 133 is still not working for you, @holyjak?

I will try it tomorrow. Sadly, I have SciCloj workshop starting in 17 min and I need my repl and connection working for it.

I would be happy to try troubleshoot this when I have time. How do I debug the code to track the error down?

Usually there is a badge next to the extension icon, it indicates that reload is required.

See this, @holyjak https://github.com/BetterThanTomorrow/calva/wiki/How-to-Hack-on-Calva

(It is a lot less involved than it looks to be from that page.)

I wonder who is the author of Calva logo?

It's @jayzawrotny

I like it.

Yeah, it is awesome.