calva 2022-01-21 | Slack Archive

Max22:01:40

Has anyone else noticed that it takes the calva repl a long time to come back when an exception is thrown? I’ve seen it hang for like 5+ seconds on multiple projects when non-exceptions come back instantaneously. Not sure if that was known behavior or a bug of some kind

pez22:01:29

I recall issues return this, but it was a while ago. It was cider-nrepl that had some issue. Which version of cider-nrepl are you using? It could be some other issue off course... There is some extra processing of exceptions in Calva.

Max17:01:21

This is what calva says when it starts:

Calva is utilizing cider-nrepl and clojure-lsp to create this VS Code experience.
  nREPL dependencies configured:
    nrepl: 0.9.0
    cider-nrepl: 0.27.4
    cider/piggieback: 0.5.3
  clojure-lsp version configured: latest

I’m seeing the behavior in my work project but not in a trivial scratch space project. The most noticeable difference is that the stack trace at work is a lot longer, but it might be something else

pez17:01:33

Are you using jack-in to start the project?

Max17:01:54

I wasn’t, I’ll try that

pez17:01:06

FYI. The information you posted merely states which versions are configured, and will be used if you use jack-in. We could make the message clearer, I now realize.

Max18:01:22

I’ve confirmed that versions don’t seem to matter. The slowness only seems to occur when connected to my repl server running inside a docker container. Both a calva-started repl and a non-dockerized repl throw exceptions reasonably fast

pez20:01:43

Can you check if you get similar behaviour using an nrepl client like Leiningen?

lein repl :connect <port>

It could help us isolate a bit...

Max21:01:59

It does not happen in a command-line repl

2022-01-21

Channels