Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2023-01-31

Channels

#calva
<
2023-01-31
>
jussi08:01:08

Before I update to the latest Calva (running 2.0.326) , just asking if anyone has seen this kind of clojure-lsp behavior where it behaves in a funky way, .lsp/.cache/db.transit.json is huuuge and clojure-lsp eats one full CPU and close to 9G of memory? 

-rw-r--r-- 1 jmo jmo 1.5G Jan 31 00:03 db.transit.json

jussi08:01:35

This started to happen yesterday.

pez08:01:44

Not seen it. Does it rebuild that huge thing if you delete the .cache directory?

pez08:01:00

Latest Calva is exactly the same as 326, btw.

2
jussi08:01:18

Will delete that cache and see what happens

pez08:01:24

Check in #CPABC1H61 if there are any reports you think are similar.

jussi08:01:46

whoa 

PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND 
448457 jmo       20   0   24.2g  21.8g      0 S   4.0  69.9  13:03.63 clojure-lsp
🙈

pez08:01:43

Doesn't look as it should. What's you clojureLspVersion setting in Calva?

jussi08:01:36

Yesterday, I downloaded from an external REST endpoint a large dataset and stored it in memory (`(def data ..)`) and that seemed to set clojure-lsp off...

jussi08:01:06

large meaning 27MB

jussi08:01:24

clojureLspVersion is latest

jussi08:01:52

all back to normal after deleting the db.transit.json file

pez08:01:34

clojure-lsp does not care what you load in the REPL, FYI.

jussi08:01:06

That is my understanding too. Really puzzled what bloated the transit file..

pez08:01:12

#CPABC1H61 is the channel to figure such things out. Calva only really controls which clojure-lsp binary is spawned and what its project root will be.

jussi08:01:28

👍:skin-tone-2: thank you for your help!

🙏 2
pez08:01:53

You're welcome. Please check if there are reports in #CPABC1H61 or on the repo, and if not, consider reporting it somehow. Just asking about it in #CPABC1H61 is a good start.

pez08:01:44

And if you have that file still around, keep it a while. Maybe someone wants to know stuff about it.

jussi08:01:32

I asked about it at #lsp 👍:skin-tone-2: https://clojurians.slack.com/archives/CPABC1H61/p1675155395313099

🙏 2
👍 2
jqmtor14:01:36

Hey there, I am trying to get a REPL connection without being prompted for the project kind (where I can select, deps.edn, a custom REPL sequence, etc.). I managed to not be prompted a second time, for the aliases that I want (via the custom REPL sequence), but I’d like to not be prompted at all. The documentation mentions it’s possible, but I couldn’t figure out how. Does anyone know how to achieve this?

pez14:01:42

If the documentation says it is possible, it is lying. 😃 We should probably add that feature, but as it is you need to select project type.

pez14:01:06

Please file an issue about it. You can link this issue, which is related: https://github.com/BetterThanTomorrow/calva/issues/1908

jqmtor14:01:59

Ah, got it! Will do that.

jqmtor14:01:39

In the docs, it says > There are ways to tell Calva the answers to these prompts beforehand, so that Jack-in can be a zero-prompting command. Read on. (from https://calva.io/connect/#aliases-profiles-builds) That’s where I got the idea that it would be possible to configure to not prompt.

pez15:01:15

Feel invited to PR a change to that docs page. It used to be zero-prompt, but at some point we changed that.

jqmtor01:02:03

feel free to change wording or structure to your liking. I hope it’s clear enough

jqmtor01:02:39

I’ll look into opening the docs PR as well.

❤️ 2