This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-06
Channels
- # beginners (147)
- # boot (12)
- # chestnut (12)
- # cider (22)
- # clara (10)
- # cljs-dev (6)
- # cljs-experience (3)
- # cljsrn (12)
- # clojure (58)
- # clojure-austin (3)
- # clojure-dusseldorf (25)
- # clojure-finland (20)
- # clojure-gamedev (1)
- # clojure-greece (3)
- # clojure-italy (32)
- # clojure-new-zealand (5)
- # clojure-russia (12)
- # clojure-serbia (1)
- # clojure-spec (4)
- # clojure-uk (51)
- # clojurescript (75)
- # cursive (8)
- # datomic (81)
- # fulcro (29)
- # graphql (16)
- # heroku (6)
- # incanter (1)
- # keechma (1)
- # lumo (44)
- # off-topic (21)
- # onyx (22)
- # parinfer (5)
- # portkey (40)
- # re-frame (43)
- # reagent (5)
- # spacemacs (37)
- # specter (8)
- # unrepl (3)
@martinklepsch per your comments https://github.com/boot-clj/boot/issues/639#issuecomment-327519174 : I’m running into the issue exclusively when trying to run boot via docker — and I have this suspicion that my docker image has cached a bad boot binary. how do I check the version of the installed boot-bin?
@lwhorton you can try this in a repl:
boot.user=> Boot/initialVersion
“2.7.2”
In my project’s repl this evals to 2.5.2. It’s a bit harder to get at this value inside of docker given my dockerfiles’ setup - ill get back to you on that
unfortunately I’m not able to get an accurate read on that value… my boot task will fail any time I try to run it (or its repl). the only way for it not to barf with the clojure/lang/AFunction
exception is to explicitly set the BOOT_VERSION
, which won’t give us the default value as set by the latest install.sh
@lwhorton the value of BOOT_VERSION
should not affect what is reported by Boot/initialVersion
(at least as far as I understand the code, not 100% sure myself)
Has anyone had issue with boot-reload trying to reload a file before boot-cljs has had time to write it to resources and be read to be served by your http server? (Aleph in my case; serving using ring.middleware.resource/wrap-resource)
More specifically, how quickly after a file has been added to a fileset (by boot-cljs) will it be available as a java resource for http serving?
Stack trace of root exception is empty; this is likely due to a JVM optimization that can be disabled with -XX:-OmitStackTraceInFastThrow <-- how do fix this in boot ?
can you set JVM_OPTS ?
or maybe it’s JAVA_OPTS
@qqq this is how I set it:
export BOOT_JVM_OPTIONS="-Xmx8g -client -XX:+TieredCompilation -XX:TieredStopAtLevel=1 -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -Xverify:none -XX:-OmitStackTraceInFastThrow"
@alexmiller , @richiardiandrea : figured out what I was doingwrong -- I was adding that to boot.properties, which for some reason was not working for me -- then I put it in bash profile instead, and it worked