This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-02
Channels
- # announcements (11)
- # aws (2)
- # babashka (42)
- # beginners (26)
- # calva (17)
- # cider (1)
- # clara (2)
- # clj-kondo (44)
- # clojars (30)
- # clojure (43)
- # clojure-australia (6)
- # clojure-europe (29)
- # clojure-gamedev (4)
- # clojure-greece (1)
- # clojure-nl (4)
- # clojure-spec (4)
- # clojure-uk (6)
- # clojurescript (28)
- # cursive (16)
- # data-science (1)
- # datahike (4)
- # datomic (26)
- # emacs (6)
- # events (3)
- # fulcro (11)
- # graalvm (7)
- # holy-lambda (118)
- # java (9)
- # jobs (1)
- # leiningen (3)
- # lsp (21)
- # luminus (2)
- # malli (13)
- # membrane-term (1)
- # music (1)
- # nrepl (3)
- # off-topic (38)
- # pedestal (2)
- # polylith (39)
- # re-frame (33)
- # reagent (7)
- # releases (1)
- # remote-jobs (4)
- # rewrite-clj (28)
- # ring (21)
- # sql (2)
- # tools-deps (23)
- # vim (4)
- # xtdb (15)
Accidentally ran into https://clojure.atlassian.net/browse/TDEPS-207 again. Is there a workaround to allow us to update to the latest cli version? ATM, we're stuck on 1.10.3.933.
@U083D6HK9 One thing that worked for me is that I removed unaccessible maven repos from the config file, I had the same symptoms otherwise
@U083D6HK9 latest CLI prerelease includes a speculative fix for this - would love to have any feedback if you want to try 1.10.3.1053
sorry for the delay in looking at this
Thank you for taking the time Alex. I will take a look later today and let you know. Happy holidays.
Agh, holiday delay... Just tested it out. Still getting a hang.
clojure -version 08:53:05
Clojure CLI version 1.10.3.1053
Then I run:
clojure -A... -Sforce -Stree
DEPRECATED: Libs must be qualified, change deps-deploy => deps-deploy/deps-deploy (/Users/kenny/.gitlibs/libs/com.ardoq/azure-api/4fbac2ddb9eedf0779890ae2c5bb2d1f3dcfdd7f/deps.edn)
DEPRECATED: Libs must be qualified, change deps-deploy => deps-deploy/deps-deploy (/Users/kenny/.gitlibs/libs/com.ardoq/azure-api/4fbac2ddb9eedf0779890ae2c5bb2d1f3dcfdd7f/deps.edn)
DEPRECATED: Libs must be qualified, change clj-http => clj-http/clj-http (/Users/kenny/.gitlibs/libs/com.ardoq/azure-api/4fbac2ddb9eedf0779890ae2c5bb2d1f3dcfdd7f/deps.edn)
DEPRECATED: Libs must be qualified, change clj-time => clj-time/clj-time (/Users/kenny/.gitlibs/libs/com.ardoq/azure-api/4fbac2ddb9eedf0779890ae2c5bb2d1f3dcfdd7f/deps.edn)
Downloading: org/clojure/clojure/maven-metadata.xml from datomic-cloud
And then it hangs. Would another thread dump be useful?This is such a weird issue. Something about it is non-deterministic. ~1 out of every 10 runs will succeed.
We have 2 s3 maven repos in our :mvn/repos
. I could see that affecting things for sure.
I think I have a bit more insight on this and s3 definitely is required to trigger the condition. still thinking about how to fix it but I think I understand it now at least
@U083D6HK9 with those clues, I was able to make a repro of my own, and there's a new prerelease that you can test with a fix 1.10.3.1058
Awesome! Just tested it and it works. Thank you so much for taking the time to fix this.
not sure what you're asking for? not fixed yet
-207 is relatively rare, are you actually seeing that?
IIRC, I reported it 🙂 Yes, it occurs on every CLI run on any version greater than 1.10.3.933 both locally and on CI.
Several of the recent tdeps improvements are big QoL improvements for us, so I was hoping to find a way for us to upgrade.
I can look at it on Friday