This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-30
Channels
- # bangalore-clj (1)
- # beginners (9)
- # boot (51)
- # cider (20)
- # cljs-dev (419)
- # clojars (1)
- # clojure (338)
- # clojure-brasil (64)
- # clojure-dev (7)
- # clojure-greece (2)
- # clojure-italy (3)
- # clojure-russia (10)
- # clojure-spec (127)
- # clojure-uk (12)
- # clojurebridge (2)
- # clojurescript (132)
- # core-async (8)
- # cursive (37)
- # datomic (34)
- # dirac (5)
- # events (1)
- # funcool (3)
- # hoplon (39)
- # jobs (3)
- # leiningen (3)
- # off-topic (16)
- # om (44)
- # onyx (7)
- # pedestal (20)
- # protorepl (1)
- # random (1)
- # re-frame (64)
- # reagent (6)
- # specter (4)
- # test-check (9)
- # untangled (17)
- # vim (4)
@alandipert: feels like it's silly song season... https://www.youtube.com/watch?v=d9TpRfDdyU0
@onetom omg this song
I'm trying to run JUXT's Edge sample product as per the yada manual, and I get the following exception:
: jmglov@alhana; boot dev
clojure.lang.ExceptionInfo: null
data: {:file "boot.user5759732373140997558.clj", :line 13}
java.lang.NumberFormatException: null
...
boot.user/deduce-version-from-git/invokeStatic boot.user5759732373140997558.clj: 9
boot.user/deduce-version-from-git boot.user5759732373140997558.clj: 9
@jmglov Looks like you've hit this: https://github.com/juxt/edge/issues/19
@jmglov I've just attached a patch to that issue which should fix your issue for now.
@jmglov I should have a proper fix out later today. Just want to clarify some things before I push them.
if you want to have a random function executed by boot from the command like, deftask
is very handy - but should you also then use with-pre-wrap
if you don’t build a fileset?
@borkdude it's not necessary but if you want to compose it with other tasks, either use with-pre-wrap and return a fileset or make he deftask
itself return identity
(deftask foo [] (println "foo!") identity)
no, in that case it doesn't matter
but really, just return identity 🙂
Alternatively - https://github.com/boot-clj/boot/blob/2816a053e04f41347382d10af3d9e5622b6f877b/boot/worker/src/boot/jgit.clj#L28-L30 can this take an optional parameter of whether or not it should be http://download.eclipse.org/jgit/site/4.2.0-SNAPSHOT/apidocs/org/eclipse/jgit/api/DescribeCommand.html#setLong(boolean) setLong'd before being fetched
@dominicm sure, you can call macros in macros. Just need to make sure the environment the generated code runs in was started via boot. Otherwise pods aren't there
@alandipert maybe I messed up then. I was getting an exception about argument count.
If you paste code I can look
(pod/with-call-worker
(boot.jgit/with-repo (.. repo describe call)))
I'm trying to create a variation of https://github.com/boot-clj/boot/blob/2816a053e04f41347382d10af3d9e5622b6f877b/boot/worker/src/boot/jgit.clj#L28-L30Gives me:
clojure.lang.Compiler$CompilerException: clojure.lang.ArityException: Wrong number of args (1) passed to: jgit/with-repo, compiling:(:16:1)
clojure.lang.ArityException: Wrong number of args (1) passed to: jgit/with-repo
Ah yes, I think you want woth-call-in
That one needs the first elem of list to be function, not macro
Yeah it's a special one for calling functions in the worker pod, vs running arbitrary code
The error is because macros are functions of at least 2 args, &env and &form
Ah, that makes a lot of sense, never knew that. Thanks for your help. Onto git parsing madness!
You can use your own pod
I can do it manually with 2/3 calls instead - seems fast still. Clj-jgit uses 3.7, and I don't fancy wrestling with updating / other libraries. If I package this up for others, I might try something like that though.
Cool. Yeah the pod is only really necessary if you're making a task to share
I think this has been answered before, but If I have a boot task with a ...(serve)(watch)…
in it running in my repl and stored in a future, how can I send an interrupt to that task in a way that the server gets shut down correctly
@adamfrey I think derefing the future and hitting ctrl+c should do that
for some reason when I do that and then try starting a new server I always get "Address Already in Use” which seems like my server isn’t stopping correctly
I tried simplifying the problem a bit, and I can’t get it to work under basic circumstances.
1) Run boot repl
from the terminal
2) eval a boot task with (serve)(watch)
from the REPL
3) Type CTRL-C in the REPL
4) my server is still running
@onetom great song
@adamfrey have you tried any other tasks like serve
to exclude that this behaviour is a bug in the serve
task?