Fork me on GitHub
Christian Johansen07:11:59

I’m seeing some strange behavior this morning… Jack in to my ClojureScript/Node.js REPL, but I never get a REPL. However, I can see that the process is started. target/node/dev/node.log is created and updated. Saving a file, I see figwheel is apparently running, but in my buffer list there is no nrepl buffer. Anyone seen anything like this?

Christian Johansen07:11:12

last line in messages is [nREPL] Starting server via /usr/local/bin/clojure -A:dev -Sdeps '{:deps {org.clojure/tools.nrepl {:mvn/version "0.2.13"} cider/piggieback {:mvn/version "0.3.9"} refactor-nrepl {:mvn/version "2.4.0"} cider/cider-nrepl {:mvn/version "0.18.0"}}}' -e '(require (quote cider-nrepl.main)) (cider-nrepl.main/init ["refactor-nrepl.middleware/wrap-refactor", "cider.nrepl/cider-middleware", "cider.piggieback/wrap-cljs-repl"])'...

Christian Johansen07:11:57

if I try to jack in again, it complains about a pre-existing process, and I suddenly get all the figwheel output etc in messages, but still no REPL

Christian Johansen07:11:05

deps.edn and figwheel-main btw

Christian Johansen07:11:22

clojure -A:dev gives me a working REPL in a terminal

Christian Johansen08:11:04

this has my head exploding, I worked with this setup just two days ago… I don’t think I changed anything, but I’m not sure. Does anyone spot any errors in my setup?


So - I finally upgraded to cidr 19 - From what I understand, I need to now use cider-jack-in-clj&cljs to start a clj and cljs repl simultaniously. However, when doing this my cider repl will no longer process anything I send it. I.e. (prn "AAA")


Anyone else seeing this?


> 2018-11-05 08:55:20.498:WARN:oejuc.AbstractLifeCycle:main: FAILED ServerConnector@3bfead8d{HTTP/1.1}{}: Address already in use Address already in use


From your log it seems that the nREPL server never managed to start, likely because of those errors.


I downgraded to 18 again and things work again. If anybody knows why send-to-repl doesn't work. I'd like to move back to 19

Christian Johansen16:11:26

@bozhidar yes, that happens on the second attempt to connect. The first attempt to connect launches the node process and runs figwheel, but I never see the nrepl process or the cider repl

Christian Johansen16:11:42

Which is the confusing bit

Christian Johansen16:11:00

I'd be curious if anyone else was able to make my sample repo work


If nobody else is seeing this? What can I look at as to what the cause may be?


Anyone know how to fix this? Using this demo: I fired up cider. Had it execute the namespace from index.cljs in the repl. Tried to inspect 'data' and it comes back with inspector error (no further info in messages nor the buffer it pops up other than the un-prettified/inspectable data record). In the compile process of shadow it says: WARNING: Use of undeclared Var app.index/data (<stdin> at 1:1) even when I just type 'data' into the repl (even tho it returns it fine). Also every time I try and inspect it it says the same thing.


Also, has anyone else had the experience of not being able to keep a function instrumented in edebug? I instrumented the function cider-inspector-render and I'm able to step thru it only once then after that I can't. Even if I re-evaluate the whole buffer then re-instrument the function it just blows right past it the next time. I have to restart emacs to get it to work again.


@petr see my answer in #spacemacs. I'm not sure but I'd look into your CLJS REPL and make sure it upgrades correctly. I've seen issues where a CLJS REPL that didn't fully complete its clj->cljs upgrade process would block evaluation


Is there a document somewhere which describes how to extend CIDER’s jack-in support to a new tool?


No, there isn’t. Basically for all tools I’ve just been copy/pasting what we had originally for lein, therefore the lame state of the jack-in codebase. I wanted to make this more structured and cleaner, but I never got to doing this.