Fork me on GitHub
#calva
<
2020-06-03
>
tiotolstoy07:06:31

im stuck with this? anyone know the fix

tiotolstoy07:06:51

what option should i choose to jackin with?

tiotolstoy07:06:46

NVM, fixed it 🙂

srijayanth08:06:08

I’m having serious issues with Calva. Unable to use it at the moment 😞

srijayanth08:06:45

I was on 2.0.89 and suddenly off late, after hitting a Save, fundamental things like backspace wouldn’t work

srijayanth08:06:58

updating to the latest version, fundamental things like forward select sexp wouldn’t work

srijayanth08:06:28

I’ve uninstalled, reinstalled

srijayanth08:06:34

I’ve upgraded to the latest version of VSCode, and some of those issues have gone away

srijayanth08:06:02

But, it wasn’t working as VSCode 1.38 or so

srijayanth08:06:16

Anyway, for now, this is again alright, but let us see

srijayanth08:06:52

Spoke too soon. Now, on save, it takes forever

srijayanth08:06:51

I would really like to get to the bottom of this, please tell me what all info you need from me @pez

srijayanth08:06:10

I don’t mind getting on a zoom session to show you what’s happening if that’ll help

pez08:06:47

Is it some specific files that makes this happen, or just any file?

pez08:06:58

I suspect it is a regexp that runs amok when formatting the document. Do you have format-on-save enabled?

srijayanth08:06:09

I disabled it

srijayanth08:06:11

and enabled it

srijayanth08:06:19

There seems to be a host of issues

srijayanth08:06:30

They are all related most likely to a save action

srijayanth08:06:39

I have code running with verbose on

srijayanth08:06:44

It isn’t a specific file

srijayanth08:06:57

I tried it on separate files, the same thing happens

srijayanth09:06:44

I did try a VSCode live share

srijayanth09:06:51

and the problems cropped up right after that

srijayanth09:06:42

You might have a point on the specific type of files

srijayanth09:06:49

handlers_test.clj ?

srijayanth09:06:56

no problems on handlers.clj

srijayanth09:06:51

@pez - this is very very likely. I am able to reproduce this

srijayanth09:06:05

I have two files, handlers.clj and handlers_test.clj

srijayanth09:06:24

upon saving of handlers.clj, everything is fine, however, on handlers_test.clj, everything runs amok as you asid

srijayanth09:06:29

format on save + _ in the filename?

srijayanth09:06:28

Ok, this is completely borked. I’ve now tried a variety of things, a variety of versions, it simply isn’t stable enough. I’ve tried going back to 1.0.90 and that issue is still there

srijayanth09:06:09

@pez - we’ve managed to find a specific form that is causing the issue we think. When we remove this specific form and save, the error doesn’t occur

srijayanth09:06:17

However, just this form on its own doesn’t cause the issue either

srijayanth09:06:26

If it helps you, I can send you the whole file and tell you which form

pez09:06:02

Yes, please do.

srijayanth09:06:29

The final form there with (deftest history …

srijayanth09:06:35

Is the offensive one

srijayanth09:06:50

You should be able to reproduce this bug by loading that specific file, modifying something and saving it

srijayanth09:06:53

then the error occurs

srijayanth09:06:03

However, loading that file, removing the last form and then saving it

srijayanth09:06:24

doesn’t cause the error

srijayanth09:06:38

I have format on save enabled here, but I suspect the same is true if you manually format

pez10:06:13

If you format the whole file, yes. But formatting more local forms should work, in that particular file.

srijayanth11:06:55

Yeah, let’s hope that helps

srijayanth11:06:55

As of now, I am going to switch to Cursive

srijayanth11:06:56

Let me know if there’s anything else I can try

pez14:06:43

I’ll let you know. When I have a fix for this, I’d like you to test of course. I’m curious if most of the breakage you have experienced lately, is really this bug.

srijayanth17:06:15

@pez very likely

srijayanth17:06:28

Almost certainly related to formatting

srijayanth17:06:44

I am half fighting and half enjoying spacemacs in the meantime

pez18:06:24

I thought it would be Cursive? 😎

srijayanth18:06:37

Calva has spoiled me. Cursive is a little long winded

srijayanth18:06:17

the way their stuff is organised is a little odd. Some things are grouped under different menus

srijayanth18:06:20

and its messy trying to find it

srijayanth18:06:33

and some of the default structural editing stuff is odd too

pez18:06:36

I'll fix Calva. I think I know how to avoid that regex.

pez20:06:21

Can you confirm?

srijayanth06:06:20

@pez - it will take me a day as I am occupied today with something else, so expect to hear from me by tomorrow. Sorry about that. Thank you for expediting this

pez06:06:50

No probs. I'll proceed with releasing it. Give it a spin when time allows.

srijayanth09:06:03

Well, yes, sort of.

srijayanth09:06:19

Upon save, with format on save enabled, the save takes forever too

srijayanth09:06:23

so something to do with formatting for sure

borkdude12:06:47

Anyone wants to try out a fix for using clj-kondo in a multi-root project? It now uses the current buffer to detect the .clj-kondo directory upwards.

borkdude12:06:34

I want to publish this plugin as alpha. Publishing [email protected] ERROR The version string '2020.5.10-alpha.1' doesn't conform to the requirements for a version. It must be one to four numbers in the range 0 to 2147483647, with each number seperated by a period. It must contain at least one non-zero number.

borkdude12:06:39

How do I do this?

borkdude12:06:47

I'm giving up on this.

borkdude12:06:59

I released a preview as 2020.5.90

pez13:06:50

I think it croaked on the dot in alpha.1. Using only dashes probably works.

borkdude15:06:01

that also didn't work

borkdude15:06:08

it croaked an all but dots and numbers.

borkdude15:06:29

also more than three dots didn't seem to be supported.

pez15:06:01

So 2020.5.10-alpha-1 didin't work? Maybe they do not allow prereleases at all...

brandon.ringe16:06:56

> It must be one to four numbers in the range 0 to 2147483647, with each number seperated by a period. Looks like that is correct ^

hoppy16:06:40

is there some secret sauce to using calva against babashka nrepl, or is that not ready yet?

borkdude17:06:46

@hoppy You'll have to start babashka with the --nrepl argument and then connect to a REPL outside of a project with Calva

hoppy18:06:27

I did that, and get a repl prompt in calva, but not sure where to go from there. It doesn't seem to want to let me eval anything in the .bb file buffer

hoppy18:06:38

oh, and does it matter what repl flavor I pick?

hoppy18:06:53

I'm just using 'generic'

hoppy18:06:53

hmm. seems to need .clj to wake calva up - that might be all that's up

hoppy19:06:28

:face_with_cowboy_hat:

borkdude19:06:24

maybe .bb is not associated with the Calva plugin?

pez19:06:50

Yeah, I don't think we associate .bb. Issue please.

pez19:06:52

Maybe you get away with just telling VS Code it is a Clojure file, @hoppy?

hoppy19:06:45

renamed it to .clj and all seems well, but ya, issue, assuming bb is the annointed standard.

borkdude19:06:37

.bb isn't really a standard. for most scripts I just use .clj

hoppy19:06:10

there is that and perhaps A thought to toss the shebang line?

hoppy19:06:20

very minor

borkdude19:06:54

what about the shebang?

pez20:06:38

I added the Generic repl type for the babashka use case, btw. Glad to hear that it felt like the right pick. 😃