Clojurians Log v2

@borkdude ctrl+c kills the terminal (and therefore the repl running in it) for me. As @chuck.cassel mentioned, it looks like for you vs code (maybe some extension?) is waiting on you to complete some chord. Maybe try disabling all extensions and then seeing if ctrl+c kills the repl/terminal. Though if some extension were binding those keys to something (some chord), it should show in your keyboard shortcuts.

On the topic of using this channel for vscode general help. I totally love it. I’m still thrilled that I can read red on black in the vs code terminal now. Since I asked here and @sogaiu didn’t have the same mental blockers as I had so he could help me look for the settings in the right place.

lol, we can use each other as work-arounds for our mental blockers...i love it 🙂

yes, this channel rocks

does anyone use the Sync Settings extension? I tried it but I can't find where it actually stores the gist

Having the same issue 😕 @stefan.toubia were you able to fix it?

the code for the plugin is here: https://github.com/borkdude/clj-kondo.lsp maybe you can run using a local version with some debug statements in it. Without any repro I can't help

I wish I knew what causes it 🙂 It works fine for hours but then suddenly some java process starts eating all CPU. And it stays even after I quit VSCode. After restart everything is fine. I’m trying to edit the same files, but it works ok.

using jps you can view which pid is related to clj-kondo

17481 clj-kondo.lsp-standalone.jar

and you can kill it of course, but other than that, I don't know. VSCode should be killing the server itself

so it might as well be a bug in VSCode

the source code of the language server itself hasn't been changed in over 4 months

Here's a similar bug: https://github.com/forcedotcom/salesforcedx-vscode/issues/968

I’ve tried to quit vscode now and kondo process was killed as well You know, maybe it is killed every time, but when it is in “100% CPU” mode it takes more time, will wait next time :thumbsup:

I use it. Afk atm so can't really check, but I'll get back to you if you don't figure it out before.

hmmm, I’ve just realized that I ran test via lein doo not sure how they work, I didn’t do their setup, but I see that it copies a lot of files to target/cljsbuild/public/... folder during start phase. Could it be the reason?

And their content, well, is a copy. Can it confuse kondo? “Oh there are more than 1 definition”, somthing like that

clj-kondo only lints files you are editing

ok, will keep an eye on it thanks:+1:

which OS are you on?

could it be some virus scanner thing maybe

macOS 10.14.6 no AV software installed It happens in the evening. Maybe OS schedules something like indexing (not sure why it affects kondo/java though), maybe something happens just b/c it works for a day and smth like memory leakage is happening

What we can do is put a bunch of debug statements in the plugin, make a vsix package and you watch the clj-kondo output panel

it should already output that it starts (and stops, but it's likely you won't see that since it only happens on workspace change )

Let’s wait, I will avoid running tests on my machine. For some reason I have a feeling that it is somehow connected. Unfortunately I don’t remember the exact day when I ran them for the first time and when the issue started to appear.

I have to leave right now but I have not found anything useful yet

clearing the config didn’t help, eventually it just gets back to a bad state and I have to kill the process

I’m also running tests fairly often in editor, I wonder if there’s any relation

I haven’t seen anything helpful in the output yet

thanks for the link @borkdude that’s a good lead, I’ll read through and see if it helps

Mine is in the gist called cloudSettings

You should be able to find its id under sync.gist key in the preferences file

so it is like this: https://gist.github.com/username/id

actually something else I noticed is the CPU for the clj-kondo extension is shooting through the roof as I type as well. That first spike was just typing a bunch of ((((((())))))), That last block I just wrote a tiny function and the CPU stayed high for 30s after I stopped

would definitely be helpful to get more verbose output on the language server, will check back in if I find out more

also, jps shows two clj-kondo processes. Only one of them is misbehaving

I do see CPU activity as I type, which is expected, but nothing abnormal. do you use one or multiple workspaces at the same time?

Can you also try disabling Calva and see if you can trigger the same problem?

@stefan.toubia @il.tmfv Added a bunch of debug statements which are visible in the clj-kondo output pane

Please install this VSIX

and keep me posted

I made the VSIX from this branch, fyi https://github.com/borkdude/clj-kondo.lsp/tree/debug

to build yourself:

script/build-server
cd vscode-extension && vsce package

oh very good point I forgot I had two workspaces open

thanks for the updates extension, I’ll test and see if I get any useful log info