This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-12
Channels
- # bangalore-clj (4)
- # beginners (40)
- # boot (53)
- # cider (34)
- # cljs-dev (9)
- # cljsrn (11)
- # clojure (113)
- # clojure-boston (5)
- # clojure-dev (9)
- # clojure-dusseldorf (4)
- # clojure-russia (8)
- # clojure-spec (11)
- # clojure-uk (12)
- # clojurescript (88)
- # cloverage (17)
- # conf-proposals (4)
- # core-async (30)
- # cursive (9)
- # datomic (107)
- # euroclojure (5)
- # hoplon (196)
- # luminus (10)
- # off-topic (20)
- # om (24)
- # om-next (1)
- # onyx (80)
- # parinfer (3)
- # pedestal (16)
- # planck (44)
- # proton (8)
- # protorepl (1)
- # re-frame (19)
- # reagent (7)
- # spacemacs (2)
- # untangled (29)
- # yada (25)
I will ask in here too, has someone ever faced Clojure (runtime) exceptions disappearing when inside a Runnable
? Disclaimer I have the uncaughtExceotionHndler
in place already..
@richiardiandrea: that's the reason for the auto-flush
print stream thing in boot
this mostly happens when the jvm exits while there are threads that are still wanting to write stack traces to stdout
My jvm is up and running and I see from that moment on that the print (clojure.logging) is not actually outputed
So you are saying that I need to flush log4j or something?
Kk I will try to follow that route
The error is a simple Cannot find seq ...runtime compile error
I'll need a repro case, it is better ;)
@jiyinyiyong: do you have a stack trace?
https://github.com/Cirru/boot-stack-server/blob/master/compiled/src/stack_server/core.clj#L21 the task is mine.
That's all the stack trace I current see. is there any options to display more stack traces?
@jiyinyiyong: boot -vvv
(# of vs controls the level)
pointing to this line https://github.com/adzerk-oss/boot-cljs/blob/master/src/adzerk/boot_cljs.clj#L73
Hmm, anyone else had problems with boot install
in a Docker container? Getting the following:
Retrieving tools.namespace-0.2.11.jar from
clojure.lang.ExceptionInfo: java.lang.Exception: can't find jar file
data: {:file "/tmp/boot.user5183811122264898316.clj", :line 7}
java.util.concurrent.ExecutionException: java.lang.Exception: can't find jar file
java.lang.Exception: can't find jar file
boot.task.built-in/fn/fn/fn/fn built_in.clj: 721
boot.core/run-tasks core.clj: 794
boot.core/boot/fn core.clj: 804
clojure.core/binding-conveyor-fn/fn core.clj: 1916
...
The Dockerfile does this:
RUN (mkdir brn \
&& curl -sL | tar xz -C brn \
&& cd brn \
&& boot install)
@vikeri: that's a really weird one. looks like the filesystem isn't synced or something? i've seen errors similar to thta (clearly related to bad data inside, on docker FS) when i was doing volume sharing on OS X ~2 yrs ago
maybe try downloading and boot install
as 2 separate RUN commands?
hmm, altho it occurs to me all the files in your case are inside docker, so volume sharing shouldn't be the culprit
@vikeri: there are docker images floating around github for boot
@flyboarder: I tried it too. Still not really working
are you mounting the filesystem from host?
there are issue with docker filesystem sync, i dont think it should cause issues when running commands like that within the container but if a path overlaps with something mounted then who knows...
@vikeri: if you are just running boot install
does boot know about the location where the tar is being extracted? it installs the jar from it’s fileset of out-put files if im not mistaken (things moved to target folder)
I think what you want is to download and extract that file from a boot task then install it, otherwise boot doesn’t know about the extracted files.
cljsjs projects have examples of downloading and extracting things
I run boot install in the right directory, I think it might be a memory issue with docker possibly. Continue investigating tomorrow
What is the easiest way to get your app's version in code after compiling an uberjar? Providing the version to the manifest?
@kenny: are you trying to load it on the server? or client side of your app? I think the best way would be to generate a ns during build that you can reference from your app
hmmm actually that might be a good thing to build into boot-semver :thumbsup:
when you call the macro in your cljs code it does git describe
in the shell and returns the result, which then gets compiled into the cljs namespace
Nice the above ^ I am sending the version.properties
along uberjar or js files.
using git tag makes it easy to link to things in github too, which is what we have in our application