This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-04
Channels
- # announcements (5)
- # beginners (56)
- # calva (2)
- # cider (30)
- # circleci (2)
- # cljsrn (90)
- # clojars (3)
- # clojure (18)
- # clojure-dev (9)
- # clojure-europe (3)
- # clojure-greece (14)
- # clojure-ireland (6)
- # clojure-italy (6)
- # clojure-nl (7)
- # clojure-norway (1)
- # clojure-spec (1)
- # clojure-sweden (3)
- # clojure-uk (14)
- # clojurescript (52)
- # cursive (5)
- # data-science (9)
- # datomic (3)
- # emacs (26)
- # expound (11)
- # figwheel (3)
- # figwheel-main (6)
- # fulcro (24)
- # garden (1)
- # graalvm (101)
- # liberator (1)
- # mount (1)
- # off-topic (1)
- # pathom (27)
- # portland-or (2)
- # reagent (13)
- # reitit (2)
- # ring (1)
- # shadow-cljs (10)
- # spacemacs (11)
- # sql (6)
Anyone know where I should start to debug a failing cider-connect? I’m connecting to a docker-compose env and it “suddenly” fails for me. I managed to create a never ending recursion earlier, not sure if that is related or not. Is there something that I maybe need to clear? “”helm-M-x: Sync nREPL request timed out (op eval code (seq (.split (System/getProperty “java.class.path”) “:”)) id 3 time-stamp 2019-07-04 14:37:15.403819000)” A bit rambling on my end …
@dpsutton sesman
needs the classpath early on, so I guess that’s what triggers the error, but generally this basic code should always work.
I guess there’s some unhandled exception that blocks this eval or something like this.
Hey, I deleted all my containers upgraded Emacs & Prelude and all the packages. Upgrade everything with homebrew and restarted my computer. Then it worked 🙂 Felt like a computer scientist.. 😳
So I was just about to work on my project, but when I ran cider-jack-in
I got this stacktrace https://pastebin.com/Hm17dq0p. It's been working fine in the past, but I'm not sure what has changed.
@nicholas.jaunsen Not sure what exactly is wrong, but I assume that upgrading to the latest CIDER and leiningen will fix the problem for you.
it'll be nice to see that green checkmarks everywhere. Can't figure out why it only happens in cask though
Now the only outstanding issue with the tests is figuring out why one test fails without lein being installed (something about cider-jack-in-clj&cljs
).
It fails if you remove the installation of lein
in the image. It wasn’t need in general, we’ve added it as a quick workaround.
Generally CIDER has no real “integration tests”, as those are a bit tricky in Emacs.
ah, at one point i deleted that test. it verifies (expect 'y-or-n-p :to-have-been-called-times 3)
which is just nonsense to me
it gives no insight into anything. I think its testing the params construction functions but it gives no particular insight. if that changed to 4 or 2 it wouldn't signal anything