This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-05
Channels
- # aws-lambda (1)
- # beginners (294)
- # boot (35)
- # cider (19)
- # cljs-dev (39)
- # cljsrn (7)
- # clojars (48)
- # clojure (266)
- # clojure-android (1)
- # clojure-brasil (1)
- # clojure-france (2)
- # clojure-greece (5)
- # clojure-italy (7)
- # clojure-mexico (1)
- # clojure-russia (24)
- # clojure-spec (10)
- # clojure-uk (31)
- # clojurescript (134)
- # consulting (7)
- # cursive (69)
- # datomic (20)
- # emacs (57)
- # events (2)
- # figwheel (2)
- # hoplon (1)
- # jobs-discuss (19)
- # luminus (33)
- # lumo (18)
- # mount (1)
- # off-topic (32)
- # om (5)
- # onyx (27)
- # pedestal (15)
- # re-frame (12)
- # reagent (28)
- # rum (2)
- # schema (2)
- # spacemacs (9)
- # unrepl (2)
- # untangled (7)
- # vim (5)
- # yada (4)
when attempting to push
more than once I am getting this error:
@flyboarder Do you mean push a snapshot or push a release?
snapshot right now
not using bootlaces
Hi I have a bug when issuing
$ boot dev
Exception in thread "main" java.util.concurrent.ExecutionException: java.lang.IllegalAccessError: tried to access method boot.App.isWindows()Z from class boot.file__init
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at boot.App.runBoot(App.java:248)
at boot.App.main(App.java:356)
Caused by: java.lang.IllegalAccessError: tried to access method boot.App.isWindows()Z from class boot.file__init
java -version is openjdk version "1.8.0_121" OpenJDK Runtime Environment (build 1.8.0_121-b13) OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode)
boot -V is
#
#Fri May 05 14:50:52 CEST 2017
BOOT_CLOJURE_NAME=org.clojure/clojure
BOOT_CLOJURE_VERSION=1.8.0
BOOT_VERSION=2.7.1
#App version: 2.3.0
i'm a running tutorial https://github.com/magomimmo/modern-cljs/blob/master/doc/second-edition/tutorial-03.md
Hi, anyone work with clojurescript/node.js on the backend via boot ? Specifically, I'd like to have the node.js clojurescript repl work in a flow of composed tasks
is there a way to support option alternatives? I have an option --pages which should be either a set of symbols or :all. I.e. I want something like p pages PAGES #{sym} | kw
@alandipert is there a way to clone the worker pod?
@flyboarder what do you mean by clone?
I mean I would like to use a pod with boot.aether like the worker pod, that isnt the worker pod
and id like to create and destroy that pod each time the task runs
@alandipert ideally i’d just like a task-local copy of the worker-pod
the way i would do it is, make my own pod that has the same deps as the worker pod
@alandipert do you know where those are found? It seems I can't use boot.aether from anywhere else?
it's a dep on clojars
Is there a reason I can't just use boot.aether?
boot.user=> (require '[boot.pod :as p])
nil
boot.user=> (def my-worker (p/make-pod {:dependencies (template [[boot/worker ~*boot-version*]])}))
#'boot.user/my-worker
boot.user=> (p/with-eval-in my-worker (require '[boot.aether :as ae]) (println ae/verify-colors))
{:signed #object[boot.from.io.aviso.ansi$bold_cyan 0x161178a0 boot.from.io.aviso.ansi$bold_cyan@161178a0], :unsigned #object[boot.from.io.aviso.ansi$bold_red 0x78fa548e boot.from.io.aviso.ansi$bold_red@78fa548e], :no-key #object[boot.from.io.aviso.ansi$bold_yellow 0x586ef0eb boot.from.io.aviso.ansi$bold_yellow@586ef0eb], :bad-sig #object[boot.from.io.aviso.ansi$bold_yellow 0x586ef0eb boot.from.io.aviso.ansi$bold_yellow@586ef0eb]}
oh, you can
ie (def my-worker (p/make-pod {:dependencies (template [[boot/aether ~*boot-version*]])}))
worker just has more random/useful stuff you may/may not need
@alandipert you are fantastic!!
that works and totally fixed the issue I was having with deploying to clojars!
If I am using a boot task from the repl (e.g. '(boot (my-task-here))' is there a way to properly terminate it somehow ? C-c C-c
(in cider) seems like a bad work-around - it aborts things mid-way and any code which got spun off into its own thread is still running
@pseud you want to setup some shutdown hooks