This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-11
Channels
- # arachne (5)
- # beginners (28)
- # boot (59)
- # cider (10)
- # cljs-dev (10)
- # cljsrn (10)
- # clojure (58)
- # clojure-brasil (2)
- # clojure-czech (9)
- # clojure-miami (1)
- # clojure-poland (2)
- # clojure-russia (12)
- # clojure-spec (16)
- # clojure-sweden (1)
- # clojure-taiwan (1)
- # clojure-uk (77)
- # clojurebridge (3)
- # clojurescript (108)
- # cursive (5)
- # datomic (25)
- # defnpodcast (2)
- # editors (1)
- # events (1)
- # funcool (24)
- # hoplon (37)
- # instaparse (1)
- # lein-figwheel (7)
- # leiningen (7)
- # luminus (3)
- # off-topic (9)
- # om (90)
- # onyx (88)
- # proton (3)
- # protorepl (9)
- # re-frame (30)
- # reagent (23)
- # rethinkdb (2)
- # untangled (33)
- # vim (1)
- # yada (6)
@myguidingstar: I found that occurrence very strange as well.
is it possible to call a task for function to happen just before quitting a running repl?
ie; just before an interrupt
@biscuitpants: check boot.core/cleanup
oh great! thank you @martinklepsch
@escherize: did you try pinning clojure via boot.properties?
Thanks, @sekao. It looks like the big difference is building cljs first, calling (target), then building clj and (target) again. Also the resource paths may affect it. Going to give it a try.
@petrus: regarding your error, do you have boot pinned via boot.properties
?
@petrus: in general calling target twice to build a single artifact seems like it could be simplified
@sekao, I’m trying to get the cljs+clj build working on Heroku, so I set env var BUILD_COMMAND=lein cljsbuild once && lein uberjar
, which throws java.lang.Exception: Unknown build identifier: &&
@martinklepsch, I have boot pinned via BOOT_VERSION=2.6.0
in boot.properties
.
Whoops, that wasn’t meant for me 🙂
@petrus: i don’t know much about heroku, sorry. you might need to somehow quote that command.
Thanks, got it working with a lein alias: :aliases {"go" ["do" ["cljsbuild" "once" "production"] ["uberjar"]]}
still fighting
I’ve now run into this issue a couple of times
only solved with :ensure-clean false
, even though my repo is clean
I don’t know what else to be looking for
@anmonteiro: git status
showed nothing to commit, working directory clean
and you still got the error about clean?
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
@alandipert: and I also suspect it’s what the reporter of that issue had too
namely this last comment: https://github.com/boot-clj/boot/issues/219#issuecomment-109819856
maybe something about the repo is confusing jgit?
https://github.com/boot-clj/boot/blob/master/boot/worker/src/boot/jgit.clj#L36-L38 is there the check happens ultimately
@alandipert: yeah, I also had a look at that
could play around with it at the repl and see what it's doing
ie (in-ns 'boot.jgit)
I suppose I could do that
@alandipert: that won’t work
also can’t (require ‘boot.jgit)
doesn’t seem to be on the classpath, somehow
@anmonteiro: it's in a pod
I haven’t used those ever, sorry
¯\(ツ)/¯
I think if you depend on [boot/worker "2.6.0"]
in a repl it would work
not 100% sure if that's the right module but should be
@martinklepsch: that would mean my repo would not be clean anymore
I don’t really want to commit that to my history too
sorry, boot repl -P worker
will get you into the worker pod where jgit stuff lives
cool, thanks! let me try that
@anmonteiro: you can always set-env! in a repl
found the culprit
(status)
{:added #{}, :changed #{}, :missing #{}, :modified #{}, :removed #{}, :untracked #{".DS_Store"}}
it doesn’t show in magit or git status
however
ah, maybe it's ignored in oyur global git prefs
it probably is
my guess is adding it to the project gitignore will fix
@alandipert: how could I test this change? which value should I use if I want to push to the local repo in the push
task?
@anmonteiro: it depends on whether you want it to let you push even if git is dirty
@anmonteiro: if you want that, then for it to not see my theory is you need to add .DS_Store
to your project's .gitignore
@alandipert: right, I did know that. What I’m asking is how could I test after making the change of putting that in gitignore
I dont’ really want to push it to clojars again
try (status)
at the repl again? should be empty
yeah, makes sense, sorry for the noise 🙂
np ! hope it works
connecting to pods via repl is boot wizard level 3.4 stuff btw
congrats on leveling up
ahah, thanks 🙂