Clojurians Log v2

Twice today the clj-kondo java process has run amok on my machine. Something in the files I am working with today probably triggers it. Anyone else seen that happen?

@pez See this thread: https://clojurians.slack.com/archives/CBE668G4R/p1600900901018900

Might be an issue with the clj-kondo extension or interaction with Calva. Not sure yet. Please install this debug plugin: and keep an issue on the clj-kondo output tab

and report issues to me

Thanks. Using the debugging build now. Let’s hope the java process runs amok again 😃

I’m running this build now. Seems I am working with things today that triggers the clj-kondo+calva combo to freak out.

thanks!

Could it be that the output window gets some funny data printed to it?

did you install .91?

.90 had funny output, that should be fixed with .91

Yes. .91. I was speculating about wether the contents of the Calva output could be what triggers the condition. But maybe not, since we have disabled all linters for it…

you disabled the rules, but clj-kondo is still linting it

can you post (maybe in a gist) the problem that clj-kondo prints to its output panel?

it should say somethig like [Error ..] blabla in case of an exception

This may be the cause of this CPU spike, if calva keeps printing to the REPL and triggers clj-kondo. But please post output so we know for sure.

We can hard code the Calva output file name in the clj-kondo plugin so it's just always ignored

but first proper diagnosis

You can maybe replicate this scenario by printing output to the REPL every second or so

and then see what happens

So far no errors and my computer is cool.

Do you see any output in the clj-kondo output panel. Like, is it trying to lint the REPL output?

Yeah, it prints when the files are changed.

changed file, linting: file:///Users/peter/Projects/app/.calva/output-window/output.calva-repl
found config dir at /Users/peter/Projects/app/.calva/output-window/.clj-kondo
publishing diagnostics

For project files it says the same thing except no file name after the message

found config dir at 

that's probably a nil:

(debug "found config dir at" dir)

I’ll notice immediately when I trigger the error, because I have my computer on my lap.

nice physical feedback and also a nice way to stay warm in these colder days

yeah!

so I think we can safely ignore output.calva-repl in the plugin right. this is just waste of clj-kondo cycles :)

> For project files it says the same thing except no file name after the message I think you might have no .clj-kondo dir for that project, right?

That’s correct.

Would it make sense to have a way to ignore dirs and/or files via the config?

so far that's not been needed, by default clj-kondo only lints .clj(s)(c) files

I'll just hardcode it for now, until clj-kondo gets support for it. This saves me doing another clj-kondo release for this one plugin only

Please install .92

diff: https://github.com/borkdude/clj-kondo.lsp/commit/878c704a229196cb97eb36e467bda051782489c7

How come it lints a .calva-repl file then?

I’ll wait installing .92 I think. I want the cpu to burn my lap up so that we can try figure out what causes the error. 😃

You have config {:linters ^:replace {}}: this will still lint the file but not report any errors

I think Calva sets the output window to Clojure mode and this will make it lint with clj-kondo probably

My question was re: > by default clj-kondo only lints .clj(s)(c) files

@pez so, this probably does it: https://github.com/borkdude/clj-kondo.lsp/blob/878c704a229196cb97eb36e467bda051782489c7/vscode-extension/src/extension.ts#L56

Clj-kondo process has also been acting up for me. Works fine for a while, then starts eating a ton of CPU. I will try to install the debug plugin when I have time.

Might be a recent interaction with Calva. Source is still unknown, but please monitor the clj-kondo output panel. This is the latest.

I use calva, I jack-in normally, evaluation works great etc. But when I do something wrong and send a snippet that contains something wrong I get quite excessive ouput like this https://gist.github.com/littleli/369b66c1ea822da7f5e5b663484048de Is this expected? It's confusing 😞

@ales.najmann This is expected, and I completely agree. I think @brandon.ringe created an issue where we collected some ideas around how to do this better. Right now I can only find this one though: https://github.com/BetterThanTomorrow/calva/issues/756

@ales.najmann @pez I found this one. Let's use this one and I'll close the other.

https://github.com/BetterThanTomorrow/calva/issues/737

This may be what I focus on next. Hopefully can in the next week or two.

You're great guys 👏

Thanks for mentioning the issue. Helps to see more demand for some issue/improvement so we know what to focus on.

Hello folks. Does anyone have problems with the default key bindings under MacOS? In my case I use calva.loadFile a lot. It’s by default bound to ctrl+alt+c enter but nothing happens when I hit ctrl+alt+c. Any tips on how to get this key binding to work?

Hi @ccidral ! Not sure I follow. What's supposed to happen when you press the first sequence is that vscode shows a message in the status bar saying that it is waiting for the next key press. That's not happening? If so, see if something else binds ctrl+alt+c.

Hi @pez that’s correct, I was expecting to see that message in the status bar, but when press ctrl+alt+c nothing happens (ie: no “waiting” message shows up in the status bar).

I’m running a brand new MacOS Catalina installation. I checked the OS’s keyboard shortcuts but couldn’t find any conflicting shortcut.

If you search for the shortcut in vscode, does that turn up anything but Calva commands?

No, I searched for ctrl+alt+c under Keyboard Shortcuts but it’s all Calva commands.