Go to definition of what tool? clojure-lsp? nREPL?

I have Calva+Babashka repl running and it does not work.

I'm not sure how calva implements go to definition (cc <!subteam^S03BGSAUPTQ|@calva-team>) - it could be a combination of lsp + REPL, or only lsp? Not sure.

Calva uses clojure-lsp for this. In theory we should fall back on nrepl if lsp fails, but we might have a bug there.

right, so what could he happening is that the clj-kondo analysis of that dep doesn't recognize the thing you navigate to, or lsp fails for some other reason, or the fallback to nrepl fails, or the bb nrepl server itself is missing something

> It seems the go to definition does not work @UGC0NEP4Y What happens when you try to go to definition? Does VS Code appear to just hang with a sort of pending animation above the editor? If so, that might be related to this issue: https://github.com/BetterThanTomorrow/calva/issues/1782. A workaround is to use an older version of clojure-lsp by downloading it from the clojure-lsp repo’s releases and setting the path to it in Calva’s settings.

If it just says there’s no definition found, then it’s probably not related.

> If it just says there’s no definition found, then it’s probably not related. Yes. That is the case.

Note that for jar include packages (compared to the git included one), the issue does not exist.

If you can put up a repro then we can try locally

Find out it does NOT work when the project is not the root project. For example, if I open the project foo in calva and open some file in foo/subproject

foo/subproject
where 
foo/subproject has a bb.edn

It has nothing to do with git imported libs, jump to definition on builtin in libs like clojure.string etc do not work too.

yeah, you should open calva in the root of the project

this is a common issue with vscode

Looks like something related with clojure-lsp on classpath discovering?

yeah

Does resolve work differently in clojure 1.10, more forgiving when class isn't found? cc @U064X3EF3

Don't remember anything like that

I can reproduce that locally

borkdude@m1 /tmp/foobar $ clj -A:clj1.9
Clojure 1.9.0
user=> (resolve 'org.graalvm.nativeimage.ProcessProperties)
ClassNotFoundException org.graalvm.nativeimage.ProcessProperties  java.net.URLClassLoader.findClass (URLClassLoader.java:445)
user=>
borkdude@m1 /tmp/foobar $ clj -A:clj1.10
Downloading: org/clojure/clojure/1.10.0/clojure-1.10.0.jar from central
Clojure 1.10.0
user=> (resolve 'org.graalvm.nativeimage.ProcessProperties)
nil

We can fix this with another try/catch around the resolve, but it's an interesting difference

You want an issue @U04V15CAJ?

Sure

clj-1403 maybe?

https://clojure.atlassian.net/browse/CLJ-1403

that's it, thanks

Here’s bb/process issue: https://github.com/babashka/process/issues/73

Fixed: https://github.com/babashka/process/blob/master/CHANGELOG.md#014

So speedy! Thanks a bunch!