What editor are you using and how did you set up clj-kondo with it?

You may need to restart your editor to trigger linting deps

Emacs + LSP but I get the same warning when launching in CLI:

mike@prestancedesign /t/nbb (upd-node-fetch-example)> clj-kondo --lint examples/node-fetch/
examples/node-fetch/example.cljs:20:18: warning: Unresolved var: p/->
linting took 143ms, errors: 0, warnings: 1

Restart your workspace with lsp-workspace-restart

and then wait

and then make an edit

Already tested without success, I retry tho.

I'll also test locally

Thanks.

lsp will always align to messages obtained by clj-kondo on the command line, right?

lsp might be using a slightly older or newer version than you have on the clj-kondo, but in 99% of the cases yes.

Hmm, removing .clj-kondo/.cache and then doing lsp-workspace-restart fixed it for me

but then again, now it doesn't report any unresolved var when I type a wrong one

Hmm, this is weird, when I do a manual:

$ clj-kondo --lint $(clojure -Spath) --dependencies
Downloading: funcool/promesa/6.1.434/promesa-6.1.434.pom from clojars
Downloading: funcool/promesa/6.1.434/promesa-6.1.434.jar from clojars

then it downloads promesa newer for the first time. I don't know what lsp was analyzing here ...

After delete the cache folder, it's solved. 👍

@UKFSJSM38 this is a mystery to me. could you try this one the nbb project when you have time?

@admin055 yeah, but you probably have the same problem as I have here: > but then again, now it doesn't report any unresolved var when I type a wrong one

I try

No it works for me.

That's not testing what I said :) Type p/foo

unresolved var != unresolved symbol

unresolved var = var from other namespace

oh sorry, misreading 🙂

It's confusing, I know

I don't think lsp analyzes any dependencies anymore now

it's done in 1 or 2 seconds which is suspiciously fast

Yes indeed, I experience the same bug.

Directly with CLI clj-kondo too.

because you haven't linted deps, that's expected. but normally lsp takes care of that

after deleting .lsp/.cache and .clj-kondo/.cache and then an lsp-workspace-restart it started working again for me

> because you haven't linted deps, that's expected. but normally lsp takes care of that OK understand. That's why you use clj-kondo --lint $(clojure -Spath) --dependencies before

indeed

that's what lsp is normally doing too

Interesting...

unless it caches stuff, and caching as we all know is hard

There is a bug on latest release regarding classpath cache, not sure it's the problem here, but it may worth try the latest master build from #clojure-lsp-builds

Perfect, thanks for the information. Will try later. 👍

It was a bug regarding a huge refactor I did about splitting cli from lib

I fixed couple days ago

Big refactors are sometimes worth it but can also be risky. That's why I hope y'all will try out babashka master before release 😰

Hahha yeah, one of the reasons I created #clojure-lsp-builds as well I'm trying to avoid big refractors as well, but that one was on backlog for some months already

#babashka-circleci-builds <--

$ bash <(curl ) --version 0.7.5-SNAPSHOT --dir .
$ ./bb

This refactor was on the list for 2 years or so ;)

Thanks both for the support!