This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-04
Channels
- # adventofcode (154)
- # announcements (1)
- # babashka (8)
- # beginners (28)
- # bristol-clojurians (3)
- # calva (131)
- # cider (43)
- # clj-kondo (14)
- # clojure (135)
- # clojure-europe (1)
- # clojure-italy (7)
- # clojure-madison (1)
- # clojure-nl (6)
- # clojure-spec (8)
- # clojure-uk (90)
- # clojurescript (47)
- # core-async (9)
- # cryogen (4)
- # cursive (12)
- # datomic (9)
- # emacs (7)
- # fulcro (5)
- # graalvm (56)
- # joker (4)
- # juxt (1)
- # leiningen (6)
- # off-topic (62)
- # pathom (4)
- # pedestal (2)
- # reagent (2)
- # reitit (5)
- # ring (2)
- # schema (4)
- # shadow-cljs (133)
- # sql (38)
- # tools-deps (10)
- # vim (28)
hi, I am using codebuild in AWS to build my app using Lein but for some of the dependencies I am getting connection resets on the pull from clojars. I have found some Maven issues that seem remarkably similar, their diagnosis was flaky container networking -- just wondering whether any one has seen this issue and whether there is simple fix to get it to do a few more retries
update: if I add a lein deps
into my build script prior to the lein cljsbuild once
I get this error in the deps
call and it gets a second crack at clojars in the lein cljsbuild step and works ... huzzar! is there some way to work out what is happening here? or to make lein a bit more tolerant of the networking issues whatever they are?
I've had the same problem building my app in Travis. I ended up doing travis_retry lein deps
, which makes Travis retry the command up to 5 times if it returns an error.
I would also like to know if there's a way to make lein more lenient here!
Wonder if it’s been an issue reported in lein before - but sounds like it may just be related to the underlying aether
lib used, or the “clj wrapping” layer pomegranate
that lein
uses
don’t see anything, but would think it’d relate to https://github.com/clj-commons/pomegranate/issues