Fork me on GitHub
#cider
<
2016-07-22
>
sundbp12:07:53

if I add test.check to a project where i use cider-nrepl/cider i seem to bomb out when i try to fire up a REPL. I can post a stack trade - wanted to check if anyone uses test.check and cider successfully first?

malabarba12:07:43

Yep. I use them just fine. @sundbp

sundbp12:07:57

ah, interesting.

anmonteiro13:07:39

PSA: if anyone regularly installs emacs from the git HEAD, the following commit breaks cider-jack-in with error in process filter: [nREPL] Direct connection failed https://github.com/emacs-mirror/emacs/commit/a066fb1ceee373c982214c28206108c5fba01bf7

malabarba16:07:53

That sounds bad

malabarba16:07:38

I'll try to reproduce

jaerme17:07:42

seeing this error when trying to jack in... error in process sentinel: Could not start nREPL server: Could not find artifact cider:cider-nrepl:jar:0.13.0 in central (https://repo1.maven.org/maven2/) Could not find artifact cider:cider-nrepl:jar:0.13.0 in clojars (https://clojars.org/repo/) This could be due to a typo in :dependencies or network issues. If you are behind a proxy, try setting the 'http_proxy' environment variable.

sundbp17:07:58

for my project, which jack’s in just fine with cider before adding a dependency on test.check 0.9.0, I see this exception which stops the REPL from starting (on cider-jack-in):

sundbp17:07:11

that’s using latest MELPA

dpsutton18:07:14

are you able to tart up a regular repl without cider?