This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-10
Channels
- # announcements (14)
- # bangalore-clj (1)
- # beginners (89)
- # calva (166)
- # cider (33)
- # clara (12)
- # clj-kondo (1)
- # cljdoc (8)
- # clojure (101)
- # clojure-austin (1)
- # clojure-colombia (7)
- # clojure-dev (14)
- # clojure-europe (5)
- # clojure-hamburg (10)
- # clojure-italy (9)
- # clojure-nl (31)
- # clojure-spec (4)
- # clojure-uk (39)
- # clojurescript (17)
- # clojutre (3)
- # code-reviews (16)
- # cursive (72)
- # data-science (1)
- # datomic (81)
- # duct (8)
- # emacs (4)
- # figwheel-main (1)
- # graalvm (2)
- # jobs (9)
- # kaocha (21)
- # lambdaisland (2)
- # luminus (4)
- # off-topic (35)
- # re-frame (1)
- # reagent (101)
- # reitit (4)
- # ring-swagger (5)
- # shadow-cljs (17)
- # sql (40)
- # tools-deps (4)
- # vim (28)
Hi, I am trying to produce a docker image that contains the release build artifact in drone ci. While attempting to run shadow-cljs release I get the following. Any hints?
[:app] Compiling ...
Killed
The command '/bin/sh -c cd my-app; clojure -A:shadow release app' returned a non-zero code: 137
which does not run any sort of overlay, but rather a virtual FS that has exponential memory growth, which is fine, you just need to be aware of it
so a couple options @iku000888
2) use a daemonless image builder. there's a few out there - kaniko, buildah, jig (JVM), makisu (i'm partial to makisu) 3) mount the host's docker socket, which is not always viable on hosted services
we can discuss more in #devops #cloud-native if you'd like, this is my day to day fun 😄
@iku000888 you can cap the memory used by the JVM via :jvm-opts ["-Xmx1G"]
in shadow-cljs.edn
. if you need I could add other ways to add that so you don't need to put it into the config
Hello, I would like to use debux (https://github.com/philoskim/debux) in my project but I was wondering how I can specify dependencies depending on the context (dev vs release).
As per the documentation, [philoskim/debux "0.5.6"] should be used in dev code and [philoskim/debux-stubs "0.5.6"] in production code
FYI, for the moment, I ended up adding [philoskim/debux "0.5.6"] in my dependencies but I made sure to only use the provided macros in a repl/comment context so that the code never get required in the release