Fork me on GitHub

@tees had that before make sure when you start you have no tab open with an old figwheel en doe full reload without cache. Then it should be fixed


Make sure you have no tab anywhere that tries to connect


ERROR nrepl.server - Unhandled REPL handler exception processing message {:op describe, :session e2fa2fab-cb8b-4e0e-87af-a275c8fe762e, :id 3} java.lang.NullPointerException at clojure.core$deref_future.invokeStatic(core.clj:2208) at clojure.core$deref.invokeStatic(core.clj:2228) at clojure.core$deref.invoke(core.clj:2214) at cider.nrepl$wrap_pprint_fn$fn__108074.invoke(nrepl.clj:85) at$wrap_conj_descriptor$fn__29336.invoke(middleware.clj:22) at cider.nrepl$wrap_tracker$fn__108194.invoke(nrepl.clj:410) at$wrap_conj_descriptor$fn__29336.invoke(middleware.clj:22) at$session$fn__29653.invoke(session.clj:192) at$wrap_conj_descriptor$fn__29336.invoke(middleware.clj:22) at cider.nrepl$wrap_version$fn__108206.invoke(nrepl.clj:429) at$wrap_conj_descriptor$fn__29336.invoke(middleware.clj:22) at$handle_STAR_.invokeStatic(server.clj:19) at$handle_STAR_.invoke(server.clj:16) at$handle$fn__29710.invoke(server.clj:28) at clojure.core$binding_conveyor_fn$fn__4676.invoke(core.clj:1938) at at at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at


If that looks familiar to anyone, ping me. It’s a remote nrepl not launched from lein. Started happening with a recent cider - the last week or two


Debugging now, but if someone has seen this, it’ll save me hours


i haven't seen it, but i know that the last changes to cider-nrepl were lazy loading dependencies. so i would use that as my initial thread


Definitely one of those recent changes. Reverting to a september snapshot fixes it.


if you create an issue, vspinu has been really really helpful and prompt with helping. he/she has a newborn but might be able to point you in the right direction if unable to fix it


Yeah - I should do that before I spend too much more time on it


well dang. maybe put a "me too" but also point out you arehitting this without running from an uberjar?


or whatever non-standard way that person was getting it?


Not using ubjerjar, but effectively we’re doing the same thing as that issue.