Fork me on GitHub
#cider
<
2019-07-04
>
kardan12:07:14

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 …

dpsutton15:07:21

That’s a strange error to see helm m-x involved

bozhidar17:07:53

@dpsutton sesman needs the classpath early on, so I guess that’s what triggers the error, but generally this basic code should always work.

bozhidar17:07:20

I guess there’s some unhandled exception that blocks this eval or something like this.

dpsutton17:07:29

@kardan if you're around i'm happy to help debug

kardan17:07:35

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

kardan17:07:39

Thanks anyway

dpsutton17:07:38

glad it went away 🙂

dpsutton17:07:45

@bozhidar PR up that makes all tests pass. bug in emacs C code 🙂

skykanin17:07:15

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.

bozhidar17:07:39

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

bozhidar17:07:50

@dpsutton Sounds like you had a lot of fun with that one! 😄

dpsutton17:07:16

up till 4 trying to find out why 🙂

bozhidar17:07:43

That’s what I call true grit! 😄

dpsutton17:07:14

it'll be nice to see that green checkmarks everywhere. Can't figure out why it only happens in cask though

bozhidar17:07:36

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

dpsutton17:07:53

there's a failing test? which one?

dpsutton17:07:17

if its cider-connection-tests it was the same issue

dpsutton17:07:37

(describe "cider-jack-in-clj&cljs" this one?

bozhidar17:07:38

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.

bozhidar17:07:20

None of the tests really run lein, so this wasn’t supposed to be needed.

bozhidar17:07:37

Generally CIDER has no real “integration tests”, as those are a bit tricky in Emacs.

dpsutton17:07:08

yeah for sure. i didn't think make test called out to lein. i'll look into it

dpsutton17:07:30

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

dpsutton17:07:10

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

dpsutton17:07:23

and removing that test removes the dependency of lein.

dpsutton18:07:08

huzzah!

👏 2
dpsutton18:07:48

i'll work on the lein stuff. annoyingly, getting weird circle test runner errors when i modify the test buffer. i think there's caching stuff going on 😕

dpsutton18:07:27

but i'm pretty sure that test is verifying that we ask for the port...