I can try to repro in some test project though

please do, this would be very valuable

can you show what is in your .clj-kondo/.cache directory

Can you show the contents of 2021.08.07-SNAPSHOT (feel free to leave out any corporate specific data)

just created a new app with lein new app hello and in it’s default core_test.clj file got the same unresolved var error

sweet!

can you make a zip archive of this project including the .clj-kondo/.cache ?

I can't reproduce the issue on my own system. So it would be valuable to have your .zip file

aah, looks like that newly created project doesn’t have .clj-kondo folder but still I am getting those errors

that's even weirder

can you also give the sqlite.db to @UKFSJSM38?

perhaps this helps

and you are sure you are not using another linter?

Sure, I will DM the sqlite.db to @UKFSJSM38

perhaps just make a .zip file of the whole project including the sqlite.db

and upload it to the issue

after you've done that, perhaps try again with a .clj-kondo directory

but please persist the state in a .zip file first

sure, I will try that. I am using VSCode IDE if that data point helps

I think I'm getting now what's going wrong....

@UKFSJSM38 I think you also need to include https://github.com/clj-kondo/clj-kondo/blob/13066e47b8418072edc15a853164a2ef73ddc75a/script/compile#L20 in the graalvm resources :)

this will fix it

your clojure-lsp doesn't have the built-in clj-kondo caches for clojure.test, etc.

@UKFSJSM38 feel free to do a similar PR for clj-kondo to move these settings to META-INF

then clojure-lsp will automatically benefit from this too

I'll also respond in the issue

also created a new issue: https://github.com/clojure-lsp/clojure-lsp/issues/548

Good debugging! Yeah, that makes sense now, I'll try fix it for the next release!

Fixed on clojure-lsp master @pratikgandhi1997! it should be available on next release

Awesome! Thanks for the super-quick fix 🙂

I'm doing just clj-kondo --parallel --lint src/.

how big is the src folder?

very big 🙂

not sure if this is a useful data point, but if I lint the src folder from the babashka repo it takes about 520 +/- 5 ms, regardless of --parallel

@U0178V2SLAY sources are grouped per directory and jar file, this is why you aren't seeing any difference

this is specifically for linting classpaths

Ah, I see, thanks!

you could speed it up by linting several different directories separately

--lint src/dir1:src/dir2 etc

Hmm, I’m almost certain I tried that. I’ll retry later and see if I can spot a difference

This:

find src -type d | xargs clj-kondo --parallel --lint

find src -type d | xargs clj-kondo --lint

strangely just clj-kondo --lint src is faster than both, not sure why

how does clj-kondo handle the situation where you supply "overlapping" directories? e.g. --lint first:first/second:first/second/third:... ?

because I think that what happens if you use find ... , I guess?

ah I see yes

clj-kondo doesn't handle that

it just lints whatever you give it

yeah, I assumed that when I got a bunch of "redefined vars" warnings when trying that find invocation :)

:)

it could probably filter this out, but I don't think it's very common to do it like this

but back to the original issue: if I supply several sibling folders with --lint src1:src2:..:srcN -> --parallel improves the performance

so I guess it's working as intended, but leveraging the benefits of --parallel when linting a project itself is tricky. which is fine, as the typical performance of clj-kondo is fast enough for most projects

right

also when you use --dependencies it will skip already linted .jar files with is another perf optimization

is that the :analyze-call stuff?

that's the "hard" option, the easy option is :macroexpand

https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md#macroexpand

ah cool, I'll check that out