Clojurians Log v2
cljsrn
hey hey, I'm trying out krell for the first time and I don't seem to be able to make the minimal setup work. I get
Connecting to MyApp unknown (192.168.57.103:5003) ...
#error {
:cause Connection timed out (Connection timed out)
:via
[{:type <http://java.net|java.net>.ConnectException
:message Connection timed out (Connection timed out)
:at [<http://java.net|java.net>.PlainSocketImpl socketConnect PlainSocketImpl.java -2]}]$ lsof -n -i tcp:5003
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
adb 21110 skuro 16u IPv4 160953 0t0 TCP 127.0.0.1:5003 (LISTEN)
java 24005 skuro 60u IPv6 158425 0t0 TCP 192.168.57.1:57250->192.168.57.103:5003 (SYN_SENT)any hint at where things could go wrong
Try to use the latest code from krell repo, as it’s been changed to not rely on zeroconf to pick up the IP & port
okido
alright, I upped the krell dep to the latest commit, restarted the app & the krell repl, there's no timeout at the moment but the emulator is stuck at Waiting for krell to load files while the REPL is stuck at Waiting for device connection on port 5001 so I guess there's no timeout anymore because there's no actual connection attempt?
What operating system? Which simulator?
My experience is that macOS and iOS loads consistently
David has been using android to work out kinks so it shouldn't be a nonstarter
It’s all very young though so surprises are likely
I'm on Linux / Genymotion Android emulator
I can’t talk to that. Sorry.
mhhh alright, I started with a fresh project, following the reagent tutorial but with the updated krell dep version, now things work!
I guess the target folder had some leftovers from the previous krell version which caused the Matrix glitch
Glad you sorted it out.
thanks for your support!
@admin055 good to know, I missed that
@skuro glad to know Android is working
@dnolen it works indeed, but I also experienced many Connection lost errors, e.g. ensure it works, leave to read up some documentation, back to the REPL and got the error
@skuro hrm that's interesting, open a issue saying that the socket connection doesn't seem to be kept alive - I will try that myself next week
This also happens with shadow-cljs, when Android is used, where the websocket connection just times out. To repair it, you’ve got to manually quit :cljs/quit and re-connect.