Fork me on GitHub
#calva
<
2021-08-24
>
grumplet16:08:04

Hmmm.. this is probably something I’ve done recently which has broken Calva jack-in, but I have no idea what and the error message isn’t helpful https://gist.github.com/gmp26/406dc44251b50132d3b085259e077017. The app is vorking, but no cljs repl connection. Anyone else met this?

pez16:08:27

I’ve seen the error message more often recently. But you are the first one that report it first working, the stop working, so maybe we can figure something out from your case… Have you changed anything in shadow-cljs.edn recently? Are you using deps.edn in combination with shadow?

grumplet16:08:02

Hi @U0ETXRFEW - interesting… I’m using shadow-cljs.edn and deps.edn. I’ve not changed the configuration for some time but I have added the scss-to-css VSCode plugin.

grumplet16:08:57

I’ll try an old version of the code and see if that still works….

grumplet16:08:24

Still broken with this error even on very old commits….

grumplet16:08:46

I’ll try uninstalling scss-to-css

grumplet17:08:26

Reverted to HEAD, and cleared out some recently installed VSCode extensions (scss-to-css, and the microsoft remote development extensions), restarted VSCode, and jacked in, connecting to :app, but not :test. And it worked:

grumplet17:08:34

So it’s one of those…..

grumplet17:08:54

I had restarted VSCode before, so I’m suspicious of the extensions.

pez17:08:41

Very odd. And if you install the extensions, one-by-one?

pez17:08:25

I can only imagine that it would be the remote extension, but my imagination has proven to be poor in similar cases before.

grumplet17:08:27

Breaks when I reinstall scss-to-css

grumplet17:08:42

• which was the last one I installed.

pez17:08:50

That is SO strange.

grumplet17:08:01

I’ll rinse and repeat to be sure.

pez17:08:22

Please file an issue about it.

grumplet17:08:15

Ugh.. uninstalled scss-to-css again and restarted, but this time it failed. 😞

pez17:08:39

Very, very strange. I’ll have a look at this tomorrow, if you file an issue. 😃

grumplet20:08:49

Yes - will do. It’s difficult to pin down but restarting VSCode from scratch is the only way I’ve found to clear the error.

grumplet20:08:05

OK - I’ve posted more context in https://gist.github.com/gmp26/406dc44251b50132d3b085259e077017, and made an issue