When (or if) are stack traces clickable? I found an old issue saying it's solved, but mine aren't clickable. https://github.com/cursive-ide/cursive/issues/204

@maxt Are none of them clickable?

No.

Simplest example

(/ 1 0)

Syntax error (ArithmeticException) compiling at (notification.clj:58:1).
Divide by zero

I guess that's not technically a stack trace, I'll make a better example

If you click the “Print last exception” button in the REPL toolwindow, do you get clickable links there?

You’re running Clojure 1.10, right? I guess I’ll need to add more patterns for the new error messages there to make those clickable too.

I do!

Yep, 1.10

Right, the issue is that the new messages don’t look like stacktrace elements, so Cursive misses them.

@maxt https://github.com/cursive-ide/cursive/issues/2142

Seems I can work around it by catching and using clojure.stacktrace to print the exceptions, then everything is clickable

Yes, that will work, or aviso/pretty if you prefer that (or just .printStackTrace)

All 1.10 messages should have a location in the first line of the form (source:line:col) although source may be REPL and col may be omitted. Although perhaps more usefully, in general any read/compile/macroexpand error is now an ex-data and carries those values as fields

anybody else having trouble with latest Cursive + IntelliJ and starting a deps REPL?

@dnolen What’s happening?

nothing?

no REPL

@cfleming ^ I see this exception

this is Cursive 1.8.1-2019.1 and IDEA 2019.1

@dnolen That is really weird - it’s in the guts of ShimDandy. Let me upgrade to 2019.1 final and try to reproduce that.

just as another data point, Cursive 1.8.1-2019.1 seems to be working just fine with a simple Deps project (pure Clojure, no ClojureScript) in IntelliJ IDEA 2019.1 (JBR 11) and Java 12. clojure.main REPL works as well.

@dnolen I can’t reproduce that, sorry, and I can’t imagine what might provoke that problem either. I’ll ask tcrawley (author of ShimDandy) if he’s ever seen that.

I'm also getting Dep sync failure

I think that's the root problem

Do you get an exception for that?

no information

just "sync failed"

tried the ClojureScript project - same problem

I think the issue might be that I was using tools.deps directly?

under Preferences

I’m not sure why that would cause a problem.

One thing you could try, go to Help | Debug Log Settings…, then enter #cursive.deps.DepsProjectResolver in the box there.

I switched back to the standard way and Invalidated Caches / Restart

REPL is working again

That is bizarre.

Hmm…

though that's because Deps sync

Is your project sync working now?

yes

I think REPL thing was red herring

Deps not syncing prevented me from doing anything

I’m not sure, it is still a really weird error, I can’t see how it could occur.

@dnolen That seems to be a really obscure ShimDandy bug, which is fixed in the latest release. I’ll upgrade for the next Cursive drop.