clojars

http://clojars.org discussion and “support”, see http://status.clojars.org for status.
Bjagg 2020-02-19T06:40:18.045300Z

Hi folks, I am trying to create my first clojar. Getting an error on the maven-metadata.xml file. It’s not being found in the repo (obviously), but it fails with a 400 Bad Request when attempting to upload. Anyone run into something similar? Anyway to see the server logs?

2020-02-19T13:39:37.045400Z

Can you share the full output of your deploy attempt?

Bjagg 2020-02-19T16:37:26.045600Z

$ lein deploy
Created /Users/bgonzalez/src/eve-api-client/target/eve-api-client-1.3.8-SNAPSHOT.jar
Wrote /Users/bgonzalez/src/eve-api-client/pom.xml
Could not find metadata org.clojars.bjagg:eve-api-client:1.3.8-SNAPSHOT/maven-metadata.xml in snapshots (<https://repo.clojars.org>)
Sending org/clojars/bjagg/eve-api-client/1.3.8-SNAPSHOT/eve-api-client-1.3.8-20200219.163650-1.jar (44k)
    to <https://repo.clojars.org/>
Sending org/clojars/bjagg/eve-api-client/1.3.8-SNAPSHOT/eve-api-client-1.3.8-20200219.163650-1.pom (3k)
    to <https://repo.clojars.org/>
Could not transfer metadata org.clojars.bjagg:eve-api-client/maven-metadata.xml from/to snapshots (<https://repo.clojars.org>): Failed to transfer file: <https://repo.clojars.org/org/clojars/bjagg/eve-api-client/maven-metadata.xml>. Return code is: 400 , ReasonPhrase:Bad Request.
Failed to retrieve remote metadata org.clojars.bjagg:eve-api-client/maven-metadata.xml: Could not transfer metadata org.clojars.bjagg:eve-api-client/maven-metadata.xml from/to snapshots (<https://repo.clojars.org>): Failed to transfer file: <https://repo.clojars.org/org/clojars/bjagg/eve-api-client/maven-metadata.xml>. Return code is: 400 , ReasonPhrase:Bad Request.

Bjagg 2020-02-19T16:38:00.045800Z

Github repo is git@github.com:bjagg/eve-api-client.git

Bjagg 2020-02-19T16:44:21.046Z

lein install works and creates a maven-metadata.xml file in my local repo

2020-02-20T01:26:30.046200Z

Thanks! Sorry for not getting back to you sooner, the day job has kept me busy. I haven't been able to recreate this. From looking in the logs on the server, I can see all of the artifacts making it there except the maven-metadata.xml - I don't see the request making it to the server for your failed deploys. That makes me think there is a problem at the fastly CDN level and that is what is returning the 400. But when I try it locally with a brand new artifact or a new snapshot version, it succeeds. What version of lein are you using (what is the output of lein version)? What version of java (output of java -version)?

👍 1
Bjagg 2020-02-20T02:08:09.046400Z

No worries 🙂

Bjagg 2020-02-20T02:08:35.046600Z

$ lein -version
Leiningen 2.9.1 on Java 1.8.0_231 Java HotSpot(TM) 64-Bit Server VM

Bjagg 2020-02-20T02:08:49.046800Z

$ java -version
java version "1.8.0_231"
Java(TM) SE Runtime Environment (build 1.8.0_231-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.231-b11, mixed mode)

Bjagg 2020-02-20T02:09:03.047Z

I’ll try deploying from Linux next chance I get

Bjagg 2020-02-20T17:42:14.055900Z

Getting the same issue in Linux. I ran lein deploy file:///tmp and found all the files expected under /tmp/org/clojars/bjagg/eve-api-client

2020-02-20T17:43:24.056100Z

Can you try deploying to https://clojars.org/repo/ and see if you get the same result? That will eliminate the CDN from the PUT requests at least

Bjagg 2020-02-20T17:45:06.056300Z

ok

Bjagg 2020-02-20T17:47:39.056500Z

W00t! That did it

2020-02-20T17:48:40.056700Z

Great! That also helps me narrow down what's happening. I plan to spend some time this evening on it to see if I can recreate it.

Bjagg 2020-02-20T17:49:54.057Z

Good luck -- let me know if you need some assistance.

2020-02-20T17:50:10.057200Z

Thanks! Will do.