This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # arachne (1)
- # aws (2)
- # beginners (123)
- # boot (22)
- # boot-dev (8)
- # chestnut (3)
- # cider (38)
- # clara (36)
- # cljs-dev (148)
- # clojars (2)
- # clojure (76)
- # clojure-austin (2)
- # clojure-greece (1)
- # clojure-italy (6)
- # clojure-russia (5)
- # clojure-spec (8)
- # clojure-uk (65)
- # clojurescript (45)
- # core-async (38)
- # cursive (9)
- # data-science (5)
- # datomic (28)
- # docs (1)
- # emacs (2)
- # fulcro (34)
- # hoplon (18)
- # jobs-discuss (7)
- # keechma (8)
- # lumo (5)
- # om (3)
- # onyx (31)
- # parinfer (1)
- # pedestal (1)
- # re-frame (20)
- # reagent (5)
- # ring-swagger (16)
- # shadow-cljs (56)
- # spacemacs (11)
- # specter (8)
- # sql (5)
- # unrepl (29)
- # yada (6)
@tsulej Just fixed this issue by pulling cider from melpa-stable instead of melpa. Hope that helps!
refactor-nrepl using a function we made obsolete and removed in
cider-nrepl. This was superseded by
with-safe-transport which handles unexpected errors automatically.
The quick fix would be to just put this temporary in
refactor-nrepl itself, but ideally it should adopt
with-safe-transport as well for the sake of consistency with the core CIDER middleware. //cc @benedek
@bozhidar Sounds good 🙂 Do you maybe have a suggestion how I can jack-in again short term? I'm still a newbie but willing to learn.
Just remove the
refactor-nrepl dependency (which I assume is auto-injected by
clj-refactor) and CIDER will work just fine.
This means you either have to remove the package
clj-refactor.el or put the following in your config:
Hi, after updating my boot.properties clojure version to 1.9, when I try to boot the cider repl I get
error in process sentinel: Could not start nREPL server: Classpath conflict: org.clojure/clojure version 1.9.0 already loaded, NOT loading version 1.2.0. I refreshed the .m2 folder and it still occurs. here's my boot properties file
BOOT_CLOJURE_NAME=org.clojure/clojure BOOT_CLOJURE_VERSION=1.9.0 BOOT_VERSION=2.7.2
No, it has nothing to do with Emacs. You’re having some problems with the dependency resolution of your Clojure project. I haven’t used
boot, so I can’t give you concrete advice what to do.
@here re. refactor-nrepl breakage: new snapshot version is on clojars. please give it spin and shout if still have problems
@benedek Thanks for the fast response. Look into using
with-safe-transport when you have time. I was hoping you had already adopted it, as it’s quite nice and simplifies the error handling a lot.
not yet unfortunately. will do tho. this incident kinda points to the direction of merging refactor-nrepl into cider-nrepl i guess
On a related note - the problem happened as I plan to move everything non-nREPL related from
cider-nrepl to this library https://github.com/clojure-emacs/orchard, so the core functionality can be shared with non-nREPL tools.
This extraction process might affect
refactor-nrepl short-term as well. And ideally we should move the core functionality from
orchard as well.
I’m also extending an invitation to everyone will to help move logic across the projects - that’s an easy way to get involved with the CIDER eco-system.
sounds cool. are we adopting tools.deps style git based deps resolution for these? when lein support arrives I mean...
I can confirm that bug with
refactor-nrepl is solved (ie. there is no exception and env works as previously). Thanks for solving it so fast.
Having lots of trouble with the latest cider for embedded nrepl (works ok using cider-jack-in)
java.lang.IllegalArgumentException: Cannot resolve cider.nrepl.middleware.pprint/handle-pprint-fn at cider.nrepl$resolve_or_fail.invokeStatic(nrepl.clj:25) at cider.nrepl$resolve_or_fail.invoke(nrepl.clj:23) at cider.nrepl$run_deferred_handler$fn__81560.invoke(nrepl.clj:38)
Investigating, but I thought I’d check and see if anyone else is seeing lots of problems with 0.17
Well, I guess this one is on me somehow. A clean test nrepl server works fine (at least for non-uberjar/AOT)… hmmm