This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-08
Channels
- # announcements (20)
- # aws (16)
- # babashka (63)
- # beginners (75)
- # calva (35)
- # cider (2)
- # clj-commons (5)
- # clj-kondo (2)
- # cljs-dev (1)
- # clojure (90)
- # clojure-australia (3)
- # clojure-europe (16)
- # clojure-france (1)
- # clojure-nl (4)
- # clojure-uk (5)
- # clojurescript (7)
- # data-science (2)
- # datahike (1)
- # datomic (39)
- # emacs (31)
- # events (2)
- # figwheel-main (1)
- # fulcro (15)
- # gratitude (8)
- # helix (17)
- # holy-lambda (1)
- # introduce-yourself (1)
- # jobs (3)
- # kaocha (2)
- # liquid (1)
- # malli (1)
- # nrepl (2)
- # other-languages (1)
- # portal (76)
- # react (19)
- # reagent (9)
- # remote-jobs (1)
- # rewrite-clj (9)
- # shadow-cljs (31)
- # tools-deps (5)
- # xtdb (11)
Performance of SCI will never be as good as compiled Clojure, but SCI tries to be as fast as possible within its constraints
Just add {:deps {java-http-clj/java-http-clj {:mvn/version "0.4.3"}}
to bb.edn
and you should be able to use it
hey guys, I have an interesting issue when using the clojure function from the tasks api - (clojure “-P”) as example. It just hangs in the CI/CD agent, can’t replicate it on my machine. I can work around it but its still pretty interesting, I wonder what I can do to troubleshoot it?
yes it does
its probably something in that environment, just idk how to know for sure what it is
would a thread dump be useful?
That might be the issue: if you are blocking this traffic and keeping the connection active or so
oh, well bb works in general very well, just when I try that function from the tasks api
sorry, I explained really badly
hmm maybe it can’t write to the location it should download?
No worries. If you look at the deps.clj repository you can see what it tries to download and also how to override that if you already downloaded the jar. Yes that is also possible
cool! babashka.impl.deps right? I will check it out - thanks!
oh yeah the jar is downloaded, will dig around more
yep its in there
I’m migrating a bash shell script to bb
so the expected clojure stuff works in there
I think its an issue with deps.clj because I installed in there
and get the same behaviour
cool, I will try some more and will write here if I find anything 🙂
have an awesome weekend!
sure, will give that a try too
yeah, just under some particular CI circumstances
so its something env specific for sure
yeah tried that, same
that’s why I’m convinced its something that prevents deps.clj from working
if you clone deps.clj there locally and insert println you might be able to find something perhaps
you can even download the deps.clj script from the root of that repo and execute it with bb
/tmp $ curl -sLO
$ bb deps.clj
Cloning:
Checking out: at 7501b461fde07ff8b91707d27fc10e3f4403a5fa
found the issue… a repo in ~/.clojure/deps.edn that doesn’t exist caused this
thanks for helping 🙂
hmmm not sure, it has different behaviour from the bash-clj, neither complain about a repo not existing
it could just be documented thats probably enough
@ULE3UT8Q5 is it possible for you to make a Dockerfile which shows this problem? or point me to where things didn't work like expected?
okay I will give it a try