This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-19
Channels
- # aleph (8)
- # announcements (43)
- # babashka (43)
- # beginners (62)
- # calva (8)
- # cider (27)
- # clj-kondo (18)
- # cljs-dev (25)
- # cljsrn (16)
- # clojure (51)
- # clojure-europe (6)
- # clojure-nl (14)
- # clojure-spec (7)
- # clojure-uk (39)
- # clojurescript (17)
- # cursive (9)
- # datascript (12)
- # datomic (16)
- # events (1)
- # fulcro (7)
- # funcool (1)
- # graalvm (2)
- # graphql (5)
- # jobs (1)
- # juxt (6)
- # kaocha (9)
- # leiningen (11)
- # luminus (1)
- # malli (1)
- # off-topic (80)
- # other-languages (2)
- # overtone (3)
- # pedestal (5)
- # quil (1)
- # re-frame (6)
- # reagent (1)
- # reitit (4)
- # rewrite-clj (5)
- # shadow-cljs (207)
- # spacemacs (1)
- # specter (4)
- # sql (1)
- # vim (14)
- # xtdb (7)
hi native people, i've been following this excellent guide to get started: https://github.com/PEZ/rn-rf-shadow
this means i'm running react native with expo and shadow-cljs. problem is, shadow-cljs keeps shutting down its workers on me, and when it does it kills internet access for my entire machine. i have to go an terminate a couple of processes simply called "init" to get things back again. any clues as to why?
i'm running with shadow-cljs watch app
and expo start
.
i'm running in WSL/Ubuntu
shadow-cljs cli version: 2.8.67
expo 3.8.0
node: v12.13.1
@conan can you define "shadow-cljs keeps shutting down its workers on me"? that is definitely not normal?
I keep trying to grab a stack trace and losing it. It says “worker shutting down” or similar and dumps a socket connect error stack trace. I’ll get one and post back, but I’m not doing anything intentional to trigger the shutdown
I know right, I'm amazed it's even possible. Must be killing something that handles networking.
I haven't been able to get the same exit stack trace, but compilation still stops at some point, and as before, if I try to run shadow-cljs watch app
again I get this error:
$ shadow-cljs watch app
shadow-cljs - config: /c/Users/conan/dev/rn-rf-shadow/shadow-cljs.edn cli version: 2.8.67 node: v12.13.1
shadow-cljs - starting via "clojure"
node-server err Error: listen EINVAL: invalid argument 0.0.0.0
at Server.setupListenHandle [as _listen2] (net.js:1284:19)
at listenInCluster (net.js:1349:12)
at Server.listen (net.js:1437:7)
at Sn (/c/Users/conan/dev/rn-rf-shadow/node_modules/shadow-cljs/cli/dist/shadow.cljs.npm.cli.js:98:105)
at lp (/c/Users/conan/dev/rn-rf-shadow/node_modules/shadow-cljs/cli/dist/shadow.cljs.npm.cli.js:124:334)
at Object.main (/c/Users/conan/dev/rn-rf-shadow/node_modules/shadow-cljs/cli/dist/shadow.cljs.npm.cli.js:182:399)
at Object.<anonymous> (/usr/local/lib/node_modules/shadow-cljs/cli/runner.js:48:7)
at Module._compile (internal/modules/cjs/loader.js:959:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
at Module.load (internal/modules/cjs/loader.js:815:32) {
code: 'EINVAL',
errno: 'EINVAL',
syscall: 'listen',
address: '0.0.0.0'
}
I have to terminate all the init
processes before I can run this again (or indeed, to get my internet back).