Fork me on GitHub
#cider
<
2018-01-12
>
callum03:01:28

@tsulej I’m getting the same issue

callum04:01:47

@tsulej Just fixed this issue by pulling cider from melpa-stable instead of melpa. Hope that helps!

vinai07:01:39

@callum Same issue here - how did you switch to melpa-stable?

bozhidar07:01:58

Hmm, seems 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.

bozhidar07:01:49

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

vinai07:01:45

@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.

bozhidar07:01:42

Just remove the refactor-nrepl dependency (which I assume is auto-injected by clj-refactor) and CIDER will work just fine.

bozhidar07:01:45

This means you either have to remove the package clj-refactor.el or put the following in your config:

bozhidar07:01:58

(setq cljr-inject-dependencies-at-jack-in nil)

theeternalpulse08:01:39

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

theeternalpulse08:01:01

before it was on the alpha version

bozhidar08:01:38

Probably you should exclude the Clojure 1.2 that’s a dependency of nREPL.

theeternalpulse08:01:57

hmm, is there a separate version variable in emacs I set?

bozhidar09:01:21

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.

benedek09:01:19

@here re. refactor-nrepl breakage: new snapshot version is on clojars. please give it spin and shout if still have problems

benedek09:01:49

thanks bug for the merging btw

bozhidar09:01:35

@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.

bozhidar09:01:40

Any time! You’re welcome!

benedek09:01:32

not yet unfortunately. will do tho. this incident kinda points to the direction of merging refactor-nrepl into cider-nrepl i guess

benedek09:01:49

they are too close 😉

bozhidar09:01:39

Yeah, that’s true.

bozhidar09:01:50

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.

bozhidar09:01:09

Eventually this will make it easier for us to support socket repls (for instance).

bozhidar09:01:01

This extraction process might affect refactor-nrepl short-term as well. And ideally we should move the core functionality from refactor-nrepl to orchard as well.

bozhidar09:01:13

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.

benedek10:01:49

sounds cool. are we adopting tools.deps style git based deps resolution for these? when lein support arrives I mean...

bozhidar10:01:22

Probably yes.

genmeblog11:01:25

I can confirm that bug with err-info in refactor-nrepl is solved (ie. there is no exception and env works as previously). Thanks for solving it so fast.

pyr21:01:19

do I understand it correctly that orchard paves the way for lein-free cider?

dominicm21:01:42

cider is already lein-free. Orchard is about an nrepl-free cider.

norman22:01:15

Having lots of trouble with the latest cider for embedded nrepl (works ok using cider-jack-in)

norman22:01:04

timeouts from cider-connect on an op-describe and

norman22:01:05

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)

norman22:01:29

Investigating, but I thought I’d check and see if anyone else is seeing lots of problems with 0.17

norman22:01:07

(this is after resolving the err-info)

norman22:01:06

Well, I guess this one is on me somehow. A clean test nrepl server works fine (at least for non-uberjar/AOT)… hmmm

norman23:01:41

If anyone is curious, it looks like the culprit was com.cemerick/austin. Having that on the classpath seems to have made cider nrepl very unhappy