Clojurians Log v2

I've identified a couple of possible issues, and have made attempts to address both. I don't think they are related, other than being related to the recent move of the repo from Rackspace Cloudfiles to S3: • maven-metadata.xml checksums being incorrect - this is the issue that @wilkerlucio was seeing. I think there was a failure to upload the sum files from the server -> s3, but I wasn't checking the results of the call, so the code would have considered it always successful. I've modified the s3 client to throw on error so we can see if that happens again • 400 Bad Request responses when trying to deploy - I was able to find 400 responses in Fastly logs, and they were all for maven-metadata.xml files. I suspect this might be related to some custom Fastly configuration we had to set short cache TTLs for the metadata files (and sums). I've removed that configuration and now instead make purge requests against Fastly's API for maven-metadata.xml files (and their checksum files) when a deploy occurs. This is a better approach anyway, since it would make the new metadata files available pretty much immediately instead of having to wait for the 60 second TTL to expire and allows us to cache metadata files that don't change for much longer, which is a cost savings. @bjagg @ambrosebs @atdixon - would y'all mind trying to deploy again at your leisure and see if you see the 400 Bad Request (or any other) error?

@tcrawley just tried again:

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8:deploy (injected-nexus-deploy) on project annotator.jvm: Failed to retrieve remote metadata typed:analyzer.jvm/maven-metadata.xml: Could not transfer metadata typed:analyzer.jvm/maven-metadata.xml from/to clojars (<https://repo.clojars.org>): Failed to transfer file <https://repo.clojars.org/typed/analyzer.jvm/maven-metadata.xml> with status code 400

btw I've never tried to deploy with this setup before, first time trying maven + clojars

:( Thanks for checking. Can you try this for me and paste back the result? curl -vv <https://repo.clojars.org/typed/analyzer.jvm/maven-metadata.xml> That gives me a 404 (as it should) instead of a 400.

And also curl -vv <https://clojars-repo-production.s3.us-east-2.amazonaws.com/typed/analyzer.jvm/maven-metadata.xml>?

Ambroses-MBP master$ curl -vv <https://repo.clojars.org/typed/analyzer.jvm/maven-metadata.xml>
*   Trying 151.101.193.128...
* TCP_NODELAY set
* Connected to <http://repo.clojars.org|repo.clojars.org> (151.101.193.128) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: C=US; ST=California; L=San Francisco; O=Fastly, Inc.; CN=<http://v.ssl.fastly.net|v.ssl.fastly.net>
*  start date: Jul 23 22:51:23 2019 GMT
*  expire date: Jul 23 22:51:23 2020 GMT
*  subjectAltName: host "<http://repo.clojars.org|repo.clojars.org>" matched cert's "<http://repo.clojars.org|repo.clojars.org>"
*  issuer: C=BE; O=GlobalSign nv-sa; CN=GlobalSign CloudSSL CA - SHA256 - G3
*  SSL certificate verify ok.
&gt; GET /typed/analyzer.jvm/maven-metadata.xml HTTP/1.1
&gt; Host: <http://repo.clojars.org|repo.clojars.org>
&gt; User-Agent: curl/7.54.0
&gt; Accept: */*
&gt;
&lt; HTTP/1.1 404 Not Found
&lt; Connection: keep-alive
&lt; Content-Length: 308
&lt; x-amz-request-id: 7FE1123EC79931C8
&lt; x-amz-id-2: rykg/sVKgBment72QhVJ1x5mRA0Z24vAghUm6x8E64EC8ahNYC8TPZrLH51fLC/qJQOJhMEqmJo=
&lt; Content-Type: application/xml
&lt; Server: AmazonS3
&lt; Accept-Ranges: bytes
&lt; Date: Fri, 21 Feb 2020 02:03:51 GMT
&lt; Via: 1.1 varnish
&lt; Age: 37
&lt; X-Served-By: cache-chi21180-CHI
&lt; X-Cache: HIT
&lt; X-Cache-Hits: 1
&lt; X-Timer: S1582250631.274112,VS0,VE0
&lt;
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
* Connection #0 to host <http://repo.clojars.org|repo.clojars.org> left intact
&lt;Error&gt;&lt;Code&gt;NoSuchKey&lt;/Code&gt;&lt;Message&gt;The specified key does not exist.&lt;/Message&gt;&lt;Key&gt;typed/analyzer.jvm/maven-metadata.xml&lt;/Key&gt;&lt;RequestId&gt;7FE1123EC79931C8&lt;/RequestId&gt;&lt;HostId&gt;rykg/sVKgBment72QhVJ1x5mRA0Z24vAghUm6x8E64EC8ahNYC8TPZrLH51fLC/qJQOJhMEqmJo=&lt;/HostId&gt;&lt;/Error&gt;%            Ambroses-MBP master$
Ambroses-MBP master$
Ambroses-MBP master$ curl -vv <https://clojars-repo-production.s3.us-east-2.amazonaws.com/typed/analyzer.jvm/maven-metadata.xml>
*   Trying 52.219.96.176...
* TCP_NODELAY set
* Connected to <http://clojars-repo-production.s3.us-east-2.amazonaws.com|clojars-repo-production.s3.us-east-2.amazonaws.com> (52.219.96.176) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: C=US; ST=Washington; L=Seattle; O=<http://Amazon.com|Amazon.com>, Inc.; CN=*.<http://s3.us-east-2.amazonaws.com|s3.us-east-2.amazonaws.com>
*  start date: Jan 31 00:00:00 2020 GMT
*  expire date: May 27 12:00:00 2021 GMT
*  subjectAltName: host "<http://clojars-repo-production.s3.us-east-2.amazonaws.com|clojars-repo-production.s3.us-east-2.amazonaws.com>" matched cert's "*.<http://s3.us-east-2.amazonaws.com|s3.us-east-2.amazonaws.com>"
*  issuer: C=US; O=DigiCert Inc; OU=<http://www.digicert.com|www.digicert.com>; CN=DigiCert Baltimore CA-2 G2
*  SSL certificate verify ok.
&gt; GET /typed/analyzer.jvm/maven-metadata.xml HTTP/1.1
&gt; Host: <http://clojars-repo-production.s3.us-east-2.amazonaws.com|clojars-repo-production.s3.us-east-2.amazonaws.com>
&gt; User-Agent: curl/7.54.0
&gt; Accept: */*
&gt;
&lt; HTTP/1.1 404 Not Found
&lt; x-amz-request-id: 3F8CC8D98C4F601A
&lt; x-amz-id-2: DvFTh3ZIUVzH2DcmHKGHkmFMdKObCLRIRNutiKhvN3ozbY0cJSOgnhTdc2XUKcvBXxN55yO/53I=
&lt; Content-Type: application/xml
&lt; Transfer-Encoding: chunked
&lt; Date: Fri, 21 Feb 2020 02:04:13 GMT
&lt; Server: AmazonS3
&lt;
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
* Connection #0 to host <http://clojars-repo-production.s3.us-east-2.amazonaws.com|clojars-repo-production.s3.us-east-2.amazonaws.com> left intact
&lt;Error&gt;&lt;Code&gt;NoSuchKey&lt;/Code&gt;&lt;Message&gt;The specified key does not exist.&lt;/Message&gt;&lt;Key&gt;typed/analyzer.jvm/maven-metadata.xml&lt;/Key&gt;&lt;RequestId&gt;3F8CC8D98C4F601A&lt;/RequestId&gt;&lt;HostId&gt;DvFTh3ZIUVzH2DcmHKGHkmFMdKObCLRIRNutiKhvN3ozbY0cJSOgnhTdc2XUKcvBXxN55yO/53I=&lt;/HostId&gt;&lt;/Error&gt;%            Ambroses-MBP master$

Hmm, that's all correct. Can you try deploying with maven again now? Fastly should have that 404 cached.

I tried again. It failed when trying to fetch the metadata file again.

@bjagg in your case, is this a metadata file that should already exist, or one for a new artifact?

It exists on the server (I reverted the URL back to http://repo.clojars.org)

What do you get if you try to curl -vv <https://repo.clojars.org/path/to/your/maven-metadata.xml>?

oh! some of my submodules seem to deploy.

[INFO] --- nexus-staging-maven-plugin:1.6.8:deploy (injected-nexus-deploy) @ annotator.jvm ---
[INFO] Performing deferred deploys (gathering into "/Users/ambrose/Projects/core.typed-frenchy64/master/target/nexus-staging/deferred")...
[INFO] Installing /Users/ambrose/Projects/core.typed-frenchy64/master/typed/annotator.jvm/target/annotator.jvm-1.0.1-SNAPSHOT.jar to /Users/ambrose/Projects/core.typed-frenchy64/master/target/nexus-staging/deferred/typed/annotator.jvm/1.0.1-SNAPSHOT/annotator.jvm-1.0.1-SNAPSHOT.jar
[INFO] Installing /Users/ambrose/Projects/core.typed-frenchy64/master/typed/annotator.jvm/pom.xml to /Users/ambrose/Projects/core.typed-frenchy64/master/target/nexus-staging/deferred/typed/annotator.jvm/1.0.1-SNAPSHOT/annotator.jvm-1.0.1-SNAPSHOT.pom
[INFO] Deploying remotely...
[INFO] Bulk deploying locally gathered artifacts from directory:
[INFO]  * Bulk deploying locally gathered snapshot artifacts
Downloading from clojars: <https://repo.clojars.org/typed/analyzer.jvm/1.0.1-SNAPSHOT/maven-metadata.xml>
Uploading to clojars: <https://repo.clojars.org/typed/analyzer.jvm/1.0.1-SNAPSHOT/analyzer.jvm-1.0.1-20200221.022554-1.jar>
Uploaded to clojars: <https://repo.clojars.org/typed/analyzer.jvm/1.0.1-SNAPSHOT/analyzer.jvm-1.0.1-20200221.022554-1.jar> (34 kB at 11 kB/s)
Uploading to clojars: <https://repo.clojars.org/typed/analyzer.jvm/1.0.1-SNAPSHOT/analyzer.jvm-1.0.1-20200221.022554-1.pom>
Uploaded to clojars: <https://repo.clojars.org/typed/analyzer.jvm/1.0.1-SNAPSHOT/analyzer.jvm-1.0.1-20200221.022554-1.pom> (1.2 kB at 392 B/s)
Downloading from clojars: <https://repo.clojars.org/typed/analyzer.jvm/maven-metadata.xml>
Uploading to clojars: <https://repo.clojars.org/typed/analyzer.jvm/1.0.1-SNAPSHOT/maven-metadata.xml>
Uploaded to clojars: <https://repo.clojars.org/typed/analyzer.jvm/1.0.1-SNAPSHOT/maven-metadata.xml> (767 B at 339 B/s)
Uploading to clojars: <https://repo.clojars.org/typed/analyzer.jvm/maven-metadata.xml>
Uploaded to clojars: <https://repo.clojars.org/typed/analyzer.jvm/maven-metadata.xml> (277 B at 93 B/s)
Downloading from clojars: <https://repo.clojars.org/typed/lib.clojure/1.0.1-SNAPSHOT/maven-metadata.xml>
Uploading to clojars: <https://repo.clojars.org/typed/lib.clojure/1.0.1-SNAPSHOT/lib.clojure-1.0.1-20200221.022606-1.jar>
Uploaded to clojars: <https://repo.clojars.org/typed/lib.clojure/1.0.1-SNAPSHOT/lib.clojure-1.0.1-20200221.022606-1.jar> (6.5 kB at 2.7 kB/s)
Uploading to clojars: <https://repo.clojars.org/typed/lib.clojure/1.0.1-SNAPSHOT/lib.clojure-1.0.1-20200221.022606-1.pom>
Uploaded to clojars: <https://repo.clojars.org/typed/lib.clojure/1.0.1-SNAPSHOT/lib.clojure-1.0.1-20200221.022606-1.pom> (1.0 kB at 427 B/s)
Downloading from clojars: <https://repo.clojars.org/typed/lib.clojure/maven-metadata.xml>
[WARNING] Could not transfer metadata typed:lib.clojure/maven-metadata.xml from/to clojars (<https://repo.clojars.org>): Failed to transfer file <https://repo.clojars.org/typed/lib.clojure/maven-metadata.xml> with status code 400
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for pom 1.0.1-SNAPSHOT:
[INFO]
[INFO] pom ................................................ SUCCESS [  0.539 s]
[INFO] typed.analyzer.common .............................. SUCCESS [  0.973 s]
[INFO] typed.analyzer.js .................................. SUCCESS [  0.235 s]
[INFO] typed.analyzer.jvm ................................. SUCCESS [  0.127 s]
[INFO] typed.runtime.jvm .................................. SUCCESS [  0.129 s]
[INFO] typed.lib.clojure .................................. SUCCESS [  0.121 s]
[INFO] typed.lang.jvm ..................................... SUCCESS [  0.131 s]
[INFO] typed.checker.jvm .................................. SUCCESS [  0.342 s]
[INFO] typed.checker.js ................................... SUCCESS [  0.167 s]
[INFO] typed.lib.core.async ............................... SUCCESS [  0.185 s]
[INFO] typed.annotator.jvm ................................ FAILURE [ 17.950 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  23.323 s
[INFO] Finished at: 2020-02-20T21:26:11-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8:deploy (injected-nexus-deploy) on project annotator.jvm: Failed to retrieve remote metadata typed:lib.clojure/maven-metadata.xml: Could not transfer metadata typed:lib.clojure/maven-metadata.xml from/to clojars (<https://repo.clojars.org>): Failed to transfer file <https://repo.clojars.org/typed/lib.clojure/maven-metadata.xml> with status code 400 -&gt; [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] <http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException>
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn &lt;goals&gt; -rf :annotator.jvm

Works when I use http://clojars.org/repo

Here’s the output for http://repo.clojars.org

$ curl -vv <https://repo.clojars.org/com/jaggedcode/eve-api-client/maven-metadata.xml>
*   Trying 151.101.41.128...
* TCP_NODELAY set
* Connected to <http://repo.clojars.org|repo.clojars.org> (151.101.41.128) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: C=US; ST=California; L=San Francisco; O=Fastly, Inc.; CN=<http://v.ssl.fastly.net|v.ssl.fastly.net>
*  start date: Jul 23 22:51:23 2019 GMT
*  expire date: Jul 23 22:51:23 2020 GMT
*  subjectAltName: host "<http://repo.clojars.org|repo.clojars.org>" matched cert's "<http://repo.clojars.org|repo.clojars.org>"
*  issuer: C=BE; O=GlobalSign nv-sa; CN=GlobalSign CloudSSL CA - SHA256 - G3
*  SSL certificate verify ok.
&gt; GET /com/jaggedcode/eve-api-client/maven-metadata.xml HTTP/1.1
&gt; Host: <http://repo.clojars.org|repo.clojars.org>
&gt; User-Agent: curl/7.64.1
&gt; Accept: */*
&gt; 
&lt; HTTP/1.1 404 Not Found
&lt; x-amz-request-id: 424004C4EE6BBC37
&lt; x-amz-id-2: hE9jdl6Nul6BTQboEsWcQle9W3TYIYN29oVBZ0X38kA1yT1kOPeqIOTE1vgzFhZXqDplscl6gfs=
&lt; Content-Type: application/xml
&lt; Server: AmazonS3
&lt; Content-Length: 319
&lt; Accept-Ranges: bytes
&lt; Date: Fri, 21 Feb 2020 02:30:25 GMT
&lt; Via: 1.1 varnish
&lt; Age: 30048
&lt; Connection: keep-alive
&lt; X-Served-By: cache-sjc10027-SJC
&lt; X-Cache: HIT
&lt; X-Cache-Hits: 1
&lt; X-Timer: S1582252225.172289,VS0,VE0
&lt; 
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
* Connection #0 to host <http://repo.clojars.org|repo.clojars.org> left intact
&lt;Error&gt;&lt;Code&gt;NoSuchKey&lt;/Code&gt;&lt;Message&gt;The specified key does not exist.&lt;/Message&gt;&lt;Key&gt;com/jaggedcode/eve-api-client/maven-metadata.xml&lt;/Key&gt;&lt;RequestId&gt;424004C4EE6BBC37&lt;/RequestId&gt;&lt;HostId&gt;hE9jdl6Nul6BTQboEsWcQle9W3TYIYN29oVBZ0X38kA1yT1kOPeqIOTE1vgzFhZXqDplscl6gfs=&lt;/HostId&gt;&lt;/Error&gt;* Closing connection 0

analyzer.jvm seems to have deployed https://clojars.org/typed/analyzer.jvm

don't see any others

Interesting. I get a 200 back:

curl -v <https://repo.clojars.org/com/jaggedcode/eve-api-client/maven-metadata.xml>
*   Trying 199.232.33.128...
* TCP_NODELAY set
* Connected to <http://repo.clojars.org|repo.clojars.org> (199.232.33.128) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: C=US; ST=California; L=San Francisco; O=Fastly, Inc.; CN=<http://v.ssl.fastly.net|v.ssl.fastly.net>
*  start date: Jul 23 22:51:23 2019 GMT
*  expire date: Jul 23 22:51:23 2020 GMT
*  subjectAltName: host "<http://repo.clojars.org|repo.clojars.org>" matched cert's "<http://repo.clojars.org|repo.clojars.org>"
*  issuer: C=BE; O=GlobalSign nv-sa; CN=GlobalSign CloudSSL CA - SHA256 - G3
*  SSL certificate verify ok.
&gt; GET /com/jaggedcode/eve-api-client/maven-metadata.xml HTTP/1.1
&gt; Host: <http://repo.clojars.org|repo.clojars.org>
&gt; User-Agent: curl/7.58.0
&gt; Accept: */*
&gt; 
&lt; HTTP/1.1 200 OK
&lt; x-amz-id-2: 6z3nH49znnd5Ny7/QE1jC0kmdTboNVvLt/V6rXy4i1LRXChJ/JBG6X2jtQR4HSLW5/M2nZe0RDA=
&lt; x-amz-request-id: C9CCD8AE87F1A8EF
&lt; Last-Modified: Thu, 20 Feb 2020 18:09:39 GMT
&lt; ETag: "93ac1c35f5687a36976222b272a50e4b"
&lt; Content-Type: application/xml
&lt; Server: AmazonS3
&lt; Content-Length: 308
&lt; Accept-Ranges: bytes
&lt; Date: Fri, 21 Feb 2020 03:16:13 GMT
&lt; Via: 1.1 varnish
&lt; Age: 89
&lt; Connection: keep-alive
&lt; X-Served-By: cache-fty21335-FTY
&lt; X-Cache: HIT
&lt; X-Cache-Hits: 1
&lt; X-Timer: S1582254973.185725,VS0,VE0
&lt; 
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;metadata&gt;
  &lt;groupId&gt;com.jaggedcode&lt;/groupId&gt;
  &lt;artifactId&gt;eve-api-client&lt;/artifactId&gt;
  &lt;versioning&gt;
    &lt;release&gt;1.3.8&lt;/release&gt;
    &lt;versions&gt;
      &lt;version&gt;1.3.8&lt;/version&gt;
    &lt;/versions&gt;
    &lt;lastUpdated&gt;20200220180937&lt;/lastUpdated&gt;
  &lt;/versioning&gt;
&lt;/metadata&gt;
* Connection #0 to host <http://repo.clojars.org|repo.clojars.org> left intact

That's curious. Can you try one more time? If I curl https://repo.clojars.org/typed/lib.clojure/maven-metadata.xml, I get a 404, along with headers saying fastly now has it cached.

now analyzer.jvm fails again

[INFO] --- nexus-staging-maven-plugin:1.6.8:deploy (injected-nexus-deploy) @ annotator.jvm ---
[INFO] Performing deferred deploys (gathering into "/Users/ambrose/Projects/core.typed-frenchy64/master/target/nexus-staging/deferred")...
[INFO] Installing /Users/ambrose/Projects/core.typed-frenchy64/master/typed/annotator.jvm/target/annotator.jvm-1.0.1-SNAPSHOT.jar to /Users/ambrose/Projects/core.typed-frenchy64/master/target/nexus-staging/deferred/typed/annotator.jvm/1.0.1-SNAPSHOT/annotator.jvm-1.0.1-SNAPSHOT.jar
[INFO] Installing /Users/ambrose/Projects/core.typed-frenchy64/master/typed/annotator.jvm/pom.xml to /Users/ambrose/Projects/core.typed-frenchy64/master/target/nexus-staging/deferred/typed/annotator.jvm/1.0.1-SNAPSHOT/annotator.jvm-1.0.1-SNAPSHOT.pom
[INFO] Deploying remotely...
[INFO] Bulk deploying locally gathered artifacts from directory:
[INFO]  * Bulk deploying locally gathered snapshot artifacts
Downloading from clojars: <https://repo.clojars.org/typed/analyzer.jvm/1.0.1-SNAPSHOT/maven-metadata.xml>
Downloaded from clojars: <https://repo.clojars.org/typed/analyzer.jvm/1.0.1-SNAPSHOT/maven-metadata.xml> (767 B at 743 B/s)
Uploading to clojars: <https://repo.clojars.org/typed/analyzer.jvm/1.0.1-SNAPSHOT/analyzer.jvm-1.0.1-20200221.033011-2.jar>
Uploaded to clojars: <https://repo.clojars.org/typed/analyzer.jvm/1.0.1-SNAPSHOT/analyzer.jvm-1.0.1-20200221.033011-2.jar> (34 kB at 13 kB/s)
Uploading to clojars: <https://repo.clojars.org/typed/analyzer.jvm/1.0.1-SNAPSHOT/analyzer.jvm-1.0.1-20200221.033011-2.pom>
Uploaded to clojars: <https://repo.clojars.org/typed/analyzer.jvm/1.0.1-SNAPSHOT/analyzer.jvm-1.0.1-20200221.033011-2.pom> (1.2 kB at 490 B/s)
Downloading from clojars: <https://repo.clojars.org/typed/analyzer.jvm/maven-metadata.xml>
[WARNING] Could not transfer metadata typed:analyzer.jvm/maven-metadata.xml from/to clojars (<https://repo.clojars.org>): Failed to transfer file <https://repo.clojars.org/typed/analyzer.jvm/maven-metadata.xml> with status code 400
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for pom 1.0.1-SNAPSHOT:
[INFO]
[INFO] pom ................................................ SUCCESS [  0.600 s]
[INFO] typed.analyzer.common .............................. SUCCESS [  1.290 s]
[INFO] typed.analyzer.js .................................. SUCCESS [  0.286 s]
[INFO] typed.analyzer.jvm ................................. SUCCESS [  0.179 s]
[INFO] typed.runtime.jvm .................................. SUCCESS [  0.174 s]
[INFO] typed.lib.clojure .................................. SUCCESS [  0.135 s]
[INFO] typed.lang.jvm ..................................... SUCCESS [  0.138 s]
[INFO] typed.checker.jvm .................................. SUCCESS [  0.444 s]
[INFO] typed.checker.js ................................... SUCCESS [  0.188 s]
[INFO] typed.lib.core.async ............................... SUCCESS [  0.259 s]
[INFO] typed.annotator.jvm ................................ FAILURE [  6.995 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  13.233 s
[INFO] Finished at: 2020-02-20T22:30:16-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8:deploy (injected-nexus-deploy) on project annotator.jvm: Failed to retrieve remote metadata typed:analyzer.jvm/maven-metadata.xml: Could not transfer metadata typed:analyzer.jvm/maven-metadata.xml from/to clojars (<https://repo.clojars.org>): Failed to transfer file <https://repo.clojars.org/typed/analyzer.jvm/maven-metadata.xml> with status code 400 -&gt; [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] <http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException>
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn &lt;goals&gt; -rf :annotator.jvm

IPs are different

i wasn't behind a proxy, but don't worry, seems to be working now @tcrawley