This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-25
Channels
- # beginners (21)
- # boot (37)
- # cljsjs (1)
- # cljsrn (1)
- # clojure (48)
- # clojure-greece (3)
- # clojure-poland (1)
- # clojure-quebec (4)
- # clojure-spec (40)
- # clojure-uk (1)
- # clojurescript (113)
- # cursive (13)
- # events (3)
- # hoplon (183)
- # jobs (5)
- # off-topic (2)
- # onyx (49)
- # planck (35)
- # re-frame (8)
- # reagent (2)
- # sim-testing (1)
- # specter (4)
- # spirituality-ethics (2)
- # untangled (1)
- # vim (2)
- # yada (1)
just a note, I still receive a Metaspace error
@maxp: You can add multiple paths to source paths. Is there a reason you don't want to do that?
@maxp: you usually want to copy compiled files there but instead serve them from the classpath/fileset. For deployment you might want to look at the target task
https://github.com/adzerk-oss/boot-cljs/wiki/Serving-files this might also be of interest
@martinklepsch: ^ boot-reload 0.4.10 available
@micha: are you calling .close
on the shim? That will shutdown agents for you: https://github.com/projectodd/shimdandy/blob/master/api/src/main/java/org/projectodd/shimdandy/ClojureRuntimeShim.java#L35 /cc: @richiardiandrea
@sekao: I think this option should be passed to javac task: (javac :options ["-target 1.7"])
Or (javac :options ["-target" "1.7"])
, not sure how javac handles these options
Yeah confused too here..
hello, I have a very basic boot question - i have the following boot task: `(deftask dev "Build romr-mvp for local development." [] (comp (serve :port 8000 :handler 'romr-mvp.handler/app :reload true) (watch) ; (speak) (hoplon) (reload) (cljs-repl) (cljs))) ` after starting this task the console output includes the following:
Started Jetty on http://localhost:8000 Starting file watcher (CTRL-C to quit)...
you'll see the delay when you make the first request as it fires up its threads and whatnot
so I was checking again the memory error and while we call .close
on a pod's shim, maybe the second shutdown-agents
is necessary for the the "common/boot" clojure to shutdown? another experiment/test would be to count the make-pod
against the destroy-pod
and see if they match for each watch
iteration
yes, there is a shutdown-agents
executed in the pod but it is actually not targeting the pod
because .close
on the shim does that
so that is the solution, but I haven't identified the cause