Fork me on GitHub
#cursive
<
2016-03-31
>
andrzejsliwa10:03:17

Hi Guys, anyone have idea about "No nREPL ack received” when I’m running repl in Cursive

sveri11:03:32

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

manutter5111:03:12

@cfleming: Ah, sorry, that was the project’s JVM, the IDE’s JVM is 1.8.0_40-release-b132 x86_64

andrzejsliwa12:03:44

@sveri the problem is that this is not releated to any change in app

andrzejsliwa12:03:57

some day just started doing timeouts

andrzejsliwa12:03:11

I belive its somehow releated to my macbook setup

andrzejsliwa12:03:32

I had similar before and reinstall of macosx solves problem

andrzejsliwa12:03:42

looks like routing problem or networking

sveri12:03:43

Did you raise the timeout?

andrzejsliwa12:03:10

I didn’t increase timeout, becuase I know that I didn’t change anything in source code

andrzejsliwa12:03:24

and I want to find source of problem

andrzejsliwa12:03:40

instead of extend just timeout and wait longer

sveri12:03:17

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

andrzejsliwa12:03:38

preivously extending time helps, but not in 100%

andrzejsliwa12:03:20

I would like to know how to debug such issue… how to find stacktrace and state of repl

sveri12:03:27

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.

sveri12:03:25

Not to forget about the harddrive here simple_smile

andrzejsliwa12:03:31

so even increase of time its not helping

andrzejsliwa12:03:34

No nREPL ack received Process finished with exit code 137

andrzejsliwa12:03:51

probably cursive runner its ignoring it

rauh12:03:03

@andrzejsliwa: Are you connecting to an nREPL or does Cursive start the REPL?

andrzejsliwa12:03:57

I’m starting cursive from repl

rauh12:03:39

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

rauh12:03:21

Given that it'll be tough to figure out the underlying problem.

andrzejsliwa12:03:18

the problem is that now I have this problem even from terminal

andrzejsliwa12:03:19

REPL server launch timed out.

sveri12:03:31

@rauh: Can you use the same shortcuts to send code to the nRepl?

rauh12:03:02

@sveri: AFAIK, yes. I don't miss anything. I also have fighweel running and whatnot

rauh12:03:54

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 simple_smile

sveri12:03:27

cool, thank you

cfleming21:03:31

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

bmaddy22:03:05

Does anyone know if it works to set breakpoints with clojurescript code? Run > Toggle Line Breakpoint is grayed out for me.

cfleming22:03:27

@bmaddy: No, I have a CLJS debugger planned, but Cursive doesn’t integrate with the existing JS debugger right now.

bmaddy22:03:23

@cfleming: Sounds good, thanks! I'm loving Cursive, btw. It's an absolute delight after struggling with emacs for 5yrs. Thanks!

cfleming22:03:45

@bmaddy: Thanks! I’m glad you’re enjoying it.