Fork me on GitHub

Accidentally ran into again. Is there a workaround to allow us to update to the latest cli version? ATM, we're stuck on

Dimitar Uzunov18:11:52

@U083D6HK9 One thing that worked for me is that I removed unaccessible maven repos from the config file, I had the same symptoms otherwise

Alex Miller (Clojure team)19:12:22

@U083D6HK9 latest CLI prerelease includes a speculative fix for this - would love to have any feedback if you want to try

Alex Miller (Clojure team)19:12:46

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.


Ran out of time. Will try to get to it tomorrow morning. If not, sometime next week.


Agh, holiday delay... Just tested it out. Still getting a hang.

clojure -version                                                                                                                                                                                                                         08:53:05
Clojure CLI version
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.

Alex Miller (Clojure team)15:01:53

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


Nice. Let me know if there's any info I can provide.

Alex Miller (Clojure team)02:01:15

@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


Awesome! Just tested it and it works. Thank you so much for taking the time to fix this.

Alex Miller (Clojure team)19:01:54

thx for the good reports and retests that helped me fix!

✔️ 1
Alex Miller (Clojure team)16:11:11

not sure what you're asking for? not fixed yet

Alex Miller (Clojure team)16:11:56

-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 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.

Alex Miller (Clojure team)16:11:41

I can look at it on Friday


Oh, awesome. Thank you.