This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-12
Channels
- # aleph (10)
- # beginners (62)
- # boot (12)
- # cider (97)
- # cljs-dev (171)
- # clojars (1)
- # clojure (224)
- # clojure-italy (4)
- # clojure-nl (2)
- # clojure-russia (1)
- # clojure-spec (41)
- # clojure-uk (68)
- # clojured (7)
- # clojurescript (115)
- # community-development (4)
- # cursive (2)
- # data-science (1)
- # datomic (18)
- # duct (40)
- # emacs (1)
- # events (1)
- # fulcro (148)
- # funcool (2)
- # graphql (2)
- # immutant (3)
- # jobs (3)
- # keechma (1)
- # luminus (2)
- # numerical-computing (1)
- # off-topic (19)
- # om (6)
- # parinfer (10)
- # pedestal (15)
- # precept (86)
- # reagent (12)
- # ring (3)
- # ring-swagger (2)
- # shadow-cljs (42)
- # spacemacs (19)
- # specter (17)
- # sql (11)
- # tools-deps (78)
- # unrepl (62)
- # vim (28)
$ env | grep BOOT
BOOT_JVM_OPTIONS=-Djava.library.path=/usr/local/cuda/lib64 -XX:-OmitStackTraceInFastThrow
$ cat .bashrc | grep BOOT
export BOOT_JVM_OPTIONS='-Xms36G -Xmx120G -Djava.library.path=/usr/local/cuda/lib64 -XX:-OmitStackTraceInFastThrow'
Why are the -Xms and -Xmx beings tripped off ?not sure, have you tried sourcing .bashrc and then immediately inspecting env? maybe something else is changing the env var?
maybe boot repl -e
would be a way to run the code you want
another way that comes to mind is a a ci.boot file that does (load-file "build.boot") ... your custom ci-only code
then boot -b ci.boot
oh you know what
i forgot, tasks can be ns-qualified
boot -d boot-codox codox.boot/codox -h
still possible to overwrite the codox task in its home ns but would require some real initiative of the build.boot author
@alandipert thanks Alan, using ns-qualified tasks would solve that problem perfectly, but I just realised that it doesn't really have a much sense, because entire build.boot is evaluated at the beginning, so no matter what sits in the task I'm calling, malicious code may be placed literally everywhere as a top level expression.
seems like calling boot task in an isolated container would be the only secure option.
and then not even, i don't think pods can be considered "secure"