Fork me on GitHub
Eamonn Sullivan16:01:53

Hi, I'm still getting the eldoc-related unhandled exception issue mentioned and I'm running

;; Connected to nREPL server - 
;; CIDER 1.1.0snapshot, nREPL 0.8.3
;; Clojure 1.10.2, Java 1.8.0_282
Startup: /home/linuxbrew/.linuxbrew/bin/clojure -Sdeps '{:deps {nrepl/nrepl {:mvn/version "0.8.3"} refactor-nrepl {:mvn/version "2.5.0"} cider/cider-nrepl {:mvn/version "0.25.8"}} :aliases {:cider/nrepl {:main-opts ["-m" "nrepl.cmdline" "--middleware" "[\"refactor-nrepl.middleware/wrap-refactor\",\"cider.nrepl/cider-middleware\"]"]}}}' -M:cider/nrepl
It's making cider almost unusable, because I'm getting these stack traces spewing in my REPL buffer periodically and repeatedly. I'm using emacs 28.0.50 (native comp) and straight.el. I have pulled the latest cider, etc. suggest that the issue is fixed, but that's not what I'm seeing. Do I have to be on a particular branch or something?


i'd probably try (setq cider-required-middleware-version "0.25.6") . I think 25.7 is where it started and 25.8 is what you're saying is still problematic


also, maybe try without refactor involved. i wonder if that's interacting in a weird way? I have no idea if that's even plausible but just try to whittle the problem down

Eamonn Sullivan17:01:52

I just restarted/jacked in again, but using Java 11 (instead of 8 ) and I haven't seen a stack in a few minutes now... 🤞 . I wonder if, weirdly, that has something to do with it...


quite possibly. the issues they are working around are quite technical and tricky and fundamentally relate to changes in the jvm i believe

Eamonn Sullivan17:01:49

Thanks. That'll do as a workaround for now. I normally use Java 11 for Clojure stuff, but need to use Java 8 for all of our Scala services and libraries (my actual day job). I just frequently forget to do a sudo update-alternatives --config java before starting Clojure. This will certainly act as a reminder! 🙂

Eamonn Sullivan17:01:38

Is there an issue I can track?

Eamonn Sullivan17:01:36

I see them. They already know it's a Java 8 and 9 issue, it seems.