This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-31
Channels
- # admin-announcements (1)
- # beginners (16)
- # boot (25)
- # braid-chat (7)
- # cider (4)
- # cljsfiddle (6)
- # cljsrn (1)
- # clojure (256)
- # clojure-austin (4)
- # clojure-ireland (1)
- # clojure-poland (15)
- # clojure-russia (80)
- # clojure-uk (2)
- # clojurescript (30)
- # core-async (14)
- # core-typed (3)
- # cursive (35)
- # datomic (1)
- # editors (28)
- # hoplon (32)
- # immutant (1)
- # jobs (8)
- # jobs-discuss (1)
- # juxt (6)
- # leiningen (8)
- # liberator (7)
- # off-topic (16)
- # om (69)
- # onyx (38)
- # re-frame (10)
- # spacemacs (1)
- # untangled (117)
Hi Guys, anyone have idea about "No nREPL ack received” when I’m running repl in Cursive
@andrzejsliwa: Hey, I have this happenening whenever I do a lot of stuff during repl startup and then it runs into startup timeout. You can configure that somewhere, search for repl startup timeout in the settings and raise it.
@cfleming: Ah, sorry, that was the project’s JVM, the IDE’s JVM is 1.8.0_40-release-b132 x86_64
@sveri the problem is that this is not releated to any change in app
some day just started doing timeouts
I belive its somehow releated to my macbook setup
I had similar before and reinstall of macosx solves problem
looks like routing problem or networking
I didn’t increase timeout, becuase I know that I didn’t change anything in source code
and I want to find source of problem
instead of extend just timeout and wait longer
I understand your intention, just wanted to see if it fixes the problem or not. Maybe you were close to the timeout all the time and are over the edge now
preivously extending time helps, but not in 100%
I would like to know how to debug such issue… how to find stacktrace and state of repl
Well, I want to hear @cfleming answer to this too. My assumption is just that it is a combination of code size, dependencies, your hardware, the load on your OS, leiningen version, the WLAN connection and intellij version. But, I might be wrong here, obviously.
so even increase of time its not helping
No nREPL ack received Process finished with exit code 137
probably cursive runner its ignoring it
@andrzejsliwa: Are you connecting to an nREPL or does Cursive start the REPL?
I’m starting cursive from repl
Personally I have stopped doing that. I now have all my REPLs as nREPLs and just connect Cursive to them. Made things much easier IMO
the problem is that now I have this problem even from terminal
REPL server launch timed out.
One plus: I can even load clojurescript libraries while my repl is running without a restart (vinyasa ./inject
), which AFAIK is impossible unless you have *n*REPL + Figwheel running
@andrzejsliwa: If it’s happening in the terminal too then it must be something in your application, or your environment. Do you have a firewall that might be blocking something?
Does anyone know if it works to set breakpoints with clojurescript code? Run > Toggle Line Breakpoint
is grayed out for me.
@bmaddy: No, I have a CLJS debugger planned, but Cursive doesn’t integrate with the existing JS debugger right now.