Fork me on GitHub
#chlorine
<
2020-08-18
>
fabrao14:08:17

Hello all, in Chlorine I have to execute 2 times to connect to repl, is anyone with this problem or just me?

mauricio.szabo14:08:58

I hope it's just you 😄. Which OS / Clojure version?

fabrao14:08:20

deps.edn -> :aliases {:dev {:jvm-opts ["-Dclojure.server.repl={:port,5555,:accept,clojure.core.server/repl}"]}}

fabrao14:08:34

clj -A:dev

seancorfield17:08:27

I've noticed that occasionally but haven't been able to figure out a pattern for it. I think I've only seen it happen on Windows, and it may just be that the Socket REPL is taking longer to start there and just isn't quite ready when I first connect? I'll try to pay attention next time it happens.

fabrao19:08:35

"just isn't quite ready when I first connect?" -> the repl show prompt up and after I´ll try to connect it

mauricio.szabo19:08:32

@fabrao I really don't see this issue on Linux (nor the CI server sees it 😄), but I'll try to look at it. I remember that, on some development time, I saw these problems happening but they are like a Shroendinger's Bug - when I try to observe it (by adding prn for example) it does not happen 😅

seancorfield19:08:53

It depends how long the Socket REPL takes to start up in the background. It's not related to when the interactive prompt shows up in Powershell.

seancorfield19:08:49

My experience with Clojure/Java on Windows is that some network-related stuff is substantially slower to set up than on macOS/Linux.

fabrao19:08:12

oh, I didn´t know Socket REPL starts in background, maybe the problem so

mauricio.szabo19:08:07

My experience with Linux is that the Socket REPL starts even before a prompt appears... I have no idea if it's slower on Windows, but probably is. @fabrao, you can check if the Socket REPL is online by trying to telnet into that port. If it is, indeed, online, then it's probably a bug on Chlorine side

fabrao19:08:28

I´ll try to wait more time to connect it