Clojurians Log v2

Release requires deps to call out to all maven repos and ask for more metadata, to discover the newest version - I think if you have particularly slow repos in your list that could obviously be slower.

how many libs have “RELEASE” in your setup?

Could be something else going on but that would be my first guess

There may also be some places where caching is avoided too

> think if you have particularly slow repos the only one is datomic-cloud s3 url > how many libs have “RELEASE” in your setup? adding just one RELEASE dep makes the startup time go from basically instant to about a minute Overall it's a good excuse to get rid of the RELEASE deps but if it seems worth digging into i could try to make a minimal repro at some point

The datomic s3 is particularly bad because it doesn’t even have the metadata

metadata are separate poms from the artifacts?

Neither of those, maven repos have separate files for this

The s3 one also requires spinning up aws api which uses core.async

But the 1 minute also makes me wonder if it’s agent shutdown timeout

is it actually doing anything? take some thread dumps and see if there are any running threads - ctrl-\ on *nix, ctrl-break on windows

here's a thread dump. Actually it seems to be happening with just this deps.edn:

{:deps {org.clojure/clojure       {:mvn/version "1.12.1"}
        org.clojure/core.async {:mvn/version "RELEASE"}}
 :mvn/repos {"datomic-cloud" {:url ""}}
 }

Ahh... it seems to be related to my vpn. when i turn it off it's always fast. so could be some sort of rate limiting/anti spam thing related to the hosting