Alright, about the formatting, we could ask cljfmt for performance improvements, @U016JRE24NL already helped a lot in the past with performance improvements on cljfmt side.

About the 95% , this is when clojure-lsp is analyzing the project files with kondo, we already pass the :paralel flag to kondo run in paralel, not sure there is anything we could improve there besides a better report progress bar :/

what is the size of the files in lines?

just a few hundred lines

just a few above 1k maybe

around 40k lines of clojure in total

clojure-lsp has similar project size maybe, and the 95% takes only few seconds

well maybe I have a slow disk as well, since the dev environment is inside docker

could you test on clojure-lsp project?

you can just make lint-format on clojure-lsp side

for me it takes ~5-6 secs

I actually get a syntax error

just pulled master

trying just with time clojure-lsp format instead

1 minute and 31 seconds

running clojure-lsp format on the clojure-lsp codebase

so well I guess just a slow disk

5-6s I meant the 95%

well a lot longer for that too

maybe 30 seconds

whe you run clojure-lsp for the first time in a project, it analyze the whole classpath (external analysis)

this is what takes a long time, the next time, it will use cache

but the 95% part always happen

yeah took 34 seconds the second time

in total

ok well anyway no worries was just curious

yeah, this is something I'm always trying to improve since it's the heaviest thing on clojure-lsp, next release should use Datalevin instead of sqlite which increase the cache finding (`10%`) and cache save after external analysis

but thanks for the feedback

yes, that's weird 😅

probably some misconfiguration

we get the namespaces from clj-kondo analysis

mm of what though? only thing would be clj-kondo config.edn but that doesn't mention zprint or re-frame either

alright I can try to see what clj-kondo is returniing

could you make a repro of this issue so I can investigate? this is new to me

I'll check clj-kondo output first

if I can reproduce it I'll report

it is weird because most of them are correct, just namespaces inside my project

but maybe a 10% is stuff like re-frame.subs cljs.tools.reader or other things

totally unrelated

yeah, probably a bug on clojure-lsp

a repro would help a lot I investigate

This is how clojure-lsp find the namespaces: https://github.com/clojure-lsp/clojure-lsp/blob/master/src/clojure_lsp/internal_api.clj#L115-L119

note the q/filter-project-analysis

that baiscally exclude files that come from jars

is there any chance you have these namespaces/files included not by jar

mm not really no

right I just tried on one of my open source projects

and I see the same behaviour

with this one https://github.com/andreacrotti/elo

just running clojure-lsp format on that I see all these other namespaces

should I create an issue mentioning that?

Great, please do, with a repro I can debug it :)

Oh are you Andrea from Emacs GCC?

Nvm, thats other Andrea 😅

https://github.com/clojure-lsp/clojure-lsp/issues/597

hehe no I'm another Andrea

Thank you, I'll try take a look and include on the release of this week

@andrea.crotti I can't repro with your project for some reason :thinking_face:

uh, it seems it was fixed since latest release to master

I'll double check and try to understand why

Ah right

I have the latest version but didn't try with latest master

yeah, I didn't understand yet why master fixed that 😂

I'm debugging

I think it was fixed by this commit: https://github.com/clojure-lsp/clojure-lsp/commit/eba6a4d07f17f97c788a585a2d249290be641ed3

@andrea.crotti Would you mind test on your projects as well the latest master clojure-lsp? You can generate a clojure-lsp from master with just running make on clojure-lsp project

mm I see the same issue

:thinking_face:

just pulled latest master

the issue is:

when compiling the cljs project, it generate files on the resources folder

that clojure-lsp think it's related to your project

ah wait I deleted .clj-kondo

and tried again

and it doesn't do that now

so maybe it is fixed now actulaly

ah it makes, it was the kondo cache from previous release

try removing both caches, .clj-kondo/.cache and .lsp/.cache