This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-28
Channels
- # aleph (16)
- # announcements (7)
- # asami (4)
- # aws (26)
- # babashka (26)
- # babashka-sci-dev (50)
- # beginners (118)
- # biff (7)
- # calva (15)
- # cider (6)
- # clj-kondo (8)
- # cljs-experience (3)
- # clojure (30)
- # clojure-austin (26)
- # clojure-europe (20)
- # clojure-france (2)
- # clojure-ireland (1)
- # clojure-nl (3)
- # clojure-norway (2)
- # clojure-spec (7)
- # clojure-uk (6)
- # clojurescript (12)
- # community-development (5)
- # conjure (1)
- # copenhagen-clojurians (3)
- # core-typed (71)
- # cursive (3)
- # datomic (1)
- # emacs (4)
- # fulcro (2)
- # helix (2)
- # introduce-yourself (3)
- # jobs (1)
- # london-clojurians (6)
- # lsp (122)
- # malli (2)
- # missionary (5)
- # overtone (14)
- # pathom (4)
- # polylith (1)
- # reagent (4)
- # reitit (1)
- # releases (1)
- # shadow-cljs (80)
- # testing (10)
- # tools-deps (6)
- # vim (3)
- # xtdb (19)
Is there some way to “cache” the result of the The CLI will verify that both the tag and prefix sha point to the same full sha commit, and error if not
step of the gitlib fetching process? It threw me off a little that clojure -P
didn’t cover that (although it does make sense now that I realize that’s what’s going on :))
And really I’m only asking to make sure I’m not thinking about this completely wrong—it was fairly easy to work around this once I understood what was happening
How did you end up working around it? We're stripping the :git/tag
from the deps map now, which feels a little clumsy.
That’s what I did in this case
I was using the goofy docker buildkit ssh socket mechanism to hit private repos from the build container and was trying to not pass the ssh socket to a subsequent step after the -P runs
There is now an issue for this: https://clojure.atlassian.net/browse/TDEPS-223