This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-21
Channels
- # admin-announcements (4)
- # aleph (1)
- # beginners (15)
- # boot (55)
- # braveandtrue (5)
- # cider (20)
- # clara (10)
- # cljs-dev (13)
- # cljsrn (8)
- # clojure (52)
- # clojure-austin (30)
- # clojure-brasil (2)
- # clojure-india (1)
- # clojure-italy (2)
- # clojure-nl (1)
- # clojure-russia (72)
- # clojure-sdn (9)
- # clojure-taiwan (2)
- # clojure-uk (45)
- # clojurebridge (3)
- # clojured (1)
- # clojurescript (46)
- # core-matrix (1)
- # cryogen (1)
- # cursive (43)
- # datascript (12)
- # datomic (57)
- # devcards (54)
- # emacs (6)
- # funcool (21)
- # hoplon (335)
- # jobs (15)
- # jobs-rus (40)
- # ldnclj (2)
- # lein-figwheel (20)
- # off-topic (59)
- # om (157)
- # onyx (29)
- # parinfer (2)
- # pedestal (26)
- # proton (9)
- # protorepl (2)
- # reagent (3)
- # ring-swagger (4)
- # spacemacs (2)
- # untangled (17)
I see that the repl task can take a pod name to run the repl in, but what's the proper way to name a pod I create?
@tcrawley: i think so. altho i wonder if we shouldn't have a boot.pod/set-name! function also
that would be swell, but I'm fine with .setName
, just wanted to make sure there wasn't a better way
ah that makes more sense than set-name! which would promote renaming, which is probably not good
Has anyone ever got "java.io.IOException: User limit of inotify watches reached" when running a boot task? I get it from time to time in CircleCI. Never got it locally
sudo cat /proc/sys/fs/inotify/max_user_watches
shows 8192 in both my env and in circle
I'm going to create a support ticket in circle, but wanted to share it here too, in case anyone has already gone through it
is there a way to run stuff as root in circleci? that would be another workaround
the workaround would be that root isn't ulimited
hm, i think i could be wrong about that
and you're not using the watch task in this build?
sudo should be available and increasing the limit is good fix
using 100k limit on my computers, I have hit the limit some times by running multiple boots
Could be related to number of directiories in source dirs, IIRC inotify is not recursive so each directory needs a watch (I could be wrong)
Or could be related to how watch is implemented by Java NIO
also, being a virtualized environment, I'm really not sure if I'm not affected by "bad neighbors" who might also create a lot of watches... and not sure if I want to know, perhaps it's better to just increase it 😛
I think the watches are local to container, and CircleCI creates "new" container for each build
boot installs the fsevent inotify watches so it can keep track of the source files in your project
because when those change it needs to copy them into the fileset and onto the classpath
not sure though what's different in circle that makes it to reach the limit there, while it doesn't reach it in my machine, but I think I'm fine with having that unanswered
Not sure if it possible to get list of watches but using kernel tracing it is possible to get count of watches created
And starting a Boot project created 70 watches for me
@juhoteperi: you're right about the recursive thing
Okay. Large directory tree (like node_modules) will then easily use 8k limit,
Or just don't use node_modules