Looking in the server logs, I don't see any errors or failures for that file (I do see successful uploads), so I'm not sure what happened. Maybe a network blip?

Thanks. Maybe. I repeated it several times with the same effect. I'll try it again later.

Hmm. What version of lein are you using?

Leiningen 2.9.8 on Java 18-ea OpenJDK 64-Bit Server VM

Tried it again and it's the same (see full log):

$ lein deploy clojars
Warning: profile :dev-codox not found.
If there are a lot of uncached dependencies this might take a while ...
Created /home/tsl/clojure/wadogo/target/wadogo-1.0.0-SNAPSHOT.jar
Wrote /home/tsl/clojure/wadogo/pom.xml
Retrieving org/scicloj/wadogo/1.0.0-SNAPSHOT/maven-metadata.xml (1k)
    from 
Sending org/scicloj/wadogo/1.0.0-SNAPSHOT/wadogo-1.0.0-20220712.112439-8.jar (30k)
    to 
Sending org/scicloj/wadogo/1.0.0-SNAPSHOT/wadogo-1.0.0-20220712.112439-8.pom (19k)
    to 
Retrieving org/scicloj/wadogo/maven-metadata.xml (1k)
    from 
Sending org/scicloj/wadogo/1.0.0-SNAPSHOT/maven-metadata.xml (1k)
    to 
Sending org/scicloj/wadogo/maven-metadata.xml (1k)
    to 
Could not transfer metadata org.scicloj:wadogo/maven-metadata.xml from/to clojars (): Transfer failed for 
Failed to deploy metadata: Could not transfer metadata org.scicloj:wadogo/maven-metadata.xml from/to clojars (): Transfer failed for 

Ok, something is wrong with wadogo project, the other snapshot project was fully deployed (without the error at the end)

Here is what I see for the deploy you just tried:

::ffff:172.31.6.204 - generateme [12/Jul/2022:11:25:11 +0000] "PUT /repo/org/scicloj/wadogo/maven-metadata.xml HTTP/1.1" 201 5 "-" "Leiningen/2.9.8 (Java OpenJDK 64-Bit Server VM; Linux 5.10.102.1-microsoft-standard-WSL2; amd64)"

2022-07-12 11:25:11,558 [qtp28515490-79360] INFO  clojars.routes.repo | {:group "org.scicloj", :username "generateme", :headers ["x-timer" "x-forwarded-host" "fastly-orig-accept-encoding" "host" "user-agent" "cookie" "content-length" "x-forwarded-port" "x-varnish" "connection" "pragma" "fastly-client-ip" "authorization" "fastly-ff" "x-amzn-trace-id" "fastly-ssl" "x-forwarded-for" "accept-encoding" "x-forwarded-proto" "cache-store" "x-forwarded-server" "cache-control" "cdn-loop"], :trace-id #uuid "1ebbfda4-1576-49b2-938c-e1ff2b737f07", :status :success, :timestamp-version nil, :artifact "wadogo", :uri "/repo/org/scicloj/wadogo/maven-metadata.xml", :tag :upload, :version nil, :request-method :put}

But it is going through fastly, and I don't have easy access to those logs. I can try purging that file from the fastly cache and see if that helps.

It's frustrating that aether doesn't tell you if a get or put failed since it uses the same message for either failure:

Failed to deploy metadata: Could not transfer metadata org.scicloj:wadogo/maven-metadata.xml from/to clojars

it may be successfully putting, then failing to get that file. I'll purge now.

Okay, purged. Would you mind trying again?

Sure. Give me a minute.

Did it again, and the same result 😕

This is really odd. The metadata file has the correct lastUpdated value (from https://repo.clojars.org/org/scicloj/wadogo/maven-metadata.xml):

<metadata>
<groupId>org.scicloj</groupId>
<artifactId>wadogo</artifactId>
<versioning>
<versions>
<version>0.1.0-SNAPSHOT</version>
<version>1.0.0-SNAPSHOT</version>
</versions>
<lastUpdated>20220712115444</lastUpdated>
</versioning>
</metadata>

Do you see the same thing when you access that file? (asking because I'm assuming you'll hit a different fastly node)

Yes, it's the same.

I'm baffled.

Me too... It has happened first time on this repo (and ever).

Deployed today and above issue has vanished.

:thumbsup: