Cursive 2025.2-eap5 is out. It's a bugfix release, fixing a concurrency problem in the clj-kondo initialisation, and a problem with the exception reporting. clj-kondo now also now uses the public stable version and is fast! https://cursive-ide.com/blog/cursive-2025.2-eap5.html
@cfleming Cursive 2025.2-eap4 is working on 2024.3.5, but Cursive 2025.2-eap5 doesn't work. What has changed? What should I enable to make code inspections? If I downgrade to Cursive 2025.2-eap4 then everything is working as expected without any configuration. My clj-kondo version is v2025.07.26
@mike1452 Can you try the steps from https://clojurians.slack.com/archives/C0744GXCJ/p1753909766656449?thread_ts=1753758433.143589&cid=C0744GXCJ above, and see what you get in your log?
@cfleming done! see DM for log file.
btw, what is correct config here? I show you config which is set by default.
Should I set severity level to error or warning here?
@mike1452 That setting is fine, the settings are a little weird here because this doesn't work in the same way as IntelliJ's built in inspections.
In your case, it looks like an exception:
2025-08-02 01:02:38,336 [ 7216] SEVERE - #c.i.o.a.i.CoroutineExceptionHandlerImpl - Unhandled exception in [ComponentManager(ProjectImpl@816985997), com.intellij.codeWithMe.ClientIdContextElementPrecursor@49b1eb25, CoroutineName(cursive.kondo.KondoAnnotatorCoroutineScopeProvider), Dispatchers.Default]
java.lang.NoClassDefFoundError: kotlin/coroutines/jvm/internal/SpillingKt
at cursive.kondo.KondoKt.kondoShim(kondo.kt:545)
at cursive.kondo.KondoAnnotator$doAnnotate$runtime$1$1.invokeSuspend(annotator.kt:121)
I don't recognise that class, I guess it's something internal to the Kotlin coroutines. That's consistent with differences across versions too, since that class comes from the underlying platform. I'll see if I can reproduce this and fix it.did you happen to add that logging you mentioned?
@mgardner2 Yes, I did. Try this: go to Help | Diagnostic Tools | Debug Log Settings..., and add cursive.kondo.KondoAnnotator to the box there. Then reproduce the problem (e.g. go to a Clojure file, modify it and wait a couple of seconds) and then send me your log file (Help | Show log in Finder/Explorer). You can DM it here or send it to <mailto:cursive@cursive-ide.com|cursive@cursive-ide.com>.
I'm going to fix this and get a build out shortly.
Any complaints about the kondo support in this latest version, apart from MJ? There seems to be a possibility that JetBrains will ambush us with their GA release tomorrow, so if it's all working ok I'll get a stable release out. If there are more bugs I can do a point release after that.
what "project file" is it looking for? deps.edn?
> FINE - #cursive.kondo.KondoAnnotator - No project file found
Thanks Colin! I'll have more comments about the monorepo experience but I'm off this week and haven't had a chance to reply in the other threads. I'll also try to create a demo IJ workspace
@mgardner2 Yes, that's right, what is your project setup? One thing that occurs to me is that this won't work correctly in shadow-cljs projects set up using Maven, I'll have to fix that.
@imre Ok no worries we can catch up next week, I definitely want to find a solution for that. The GA date has been moved to Monday sounds like.
it's a large Java project with one module that's a mix of Clojure and Java. At the root of that module there's a deps.edn. It's a "stub" file that we've only been using for clj-kondo so far, and only contains :paths
Ok, but does that module have a pom.xml? I guess that's what is used to actually sync the module to IntelliJ, correct?
yes it does
I'm not sure what IntelliJ's logic is, but it does "see" the module as such
Right, that's the problem. I'll fix that, thanks!
wait, what's the problem?
The problem is that IntelliJ thinks your module is a Maven module, not a deps one, and the kondo integration doesn't handle that case correctly (yet)
ahh, makes sense. Thanks for digging into this