Re: Clojars deployment failing

[Alan Thompson]

I just did a `lein deploy clojars` and it worked fine.
Alan


On Wed, Feb 19, 2020 at 8:40 PM Aaron D.  wrote:

> Whelp -- Just another data point -- I got two releases through just now
> successfully. So this is intermittent or something was fixed.
>
> On Wednesday, February 19, 2020 at 10:24:47 PM UTC-6, Aaron D. wrote:
>>
>> Hey Toby
>>
>> > What do you mean by "I disabled :checksum checking for clojars"?
>>
>> I added `:checksum :ignore` to :repositories in profile.clj -- per lein
>> example here
>> 
>>
>> > $ lein version
>> Leiningen 2.9.1 on Java 1.8.0_181 Java HotSpot(TM) 64-Bit Server VM
>>
>> I tried another release just now (without the checksum config) and am
>> able to reproduce the failure -- you can see that the release/deploy is
>> successful in transferring the signed jar artifacts but the final failure
>> is something to do with checking the checksum of maven-metadata.xml (see
>> output log below).
>>
>> Let me know if I can help anyway -- by running release attempts or
>> what-have-you .. will try to jump on slack and sync up there
>>
>> $ lein release :alpha
>> [master 19022c5] Version 0.0.3-alpha8
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>> Compiling 16 source files to
>> /Users/atdixon/_work/code-sandbox/thurber/target/classes
>> Note: Some input files use or override a deprecated API.
>> Note: Recompile with -Xlint:deprecation for details.
>> Note: Some input files use unchecked or unsafe operations.
>> Note: Recompile with -Xlint:unchecked for details.
>> Created
>> /Users/atdixon/_work/code-sandbox/thurber/target/thurber-0.0.3-alpha8.jar
>> Wrote /Users/atdixon/_work/code-sandbox/thurber/pom.xml
>> Need to sign 2 files with GPG
>> [1/2] Signing
>> /Users/atdixon/_work/code-sandbox/thurber/target/thurber-0.0.3-alpha8.jar
>> with GPG
>> [2/2] Signing /Users/atdixon/_work/code-sandbox/thurber/pom.xml with GPG
>> Sending com/github/atdixon/thurber/0.0.3-alpha8/thurber-0.0.3-alpha8.jar
>> (52k)
>> to https://repo.clojars.org/
>> Sending com/github/atdixon/thurber/0.0.3-alpha8/thurber-0.0.3-alpha8.pom
>> (4k)
>> to https://repo.clojars.org/
>> Sending
>> com/github/atdixon/thurber/0.0.3-alpha8/thurber-0.0.3-alpha8.jar.asc (1k)
>> to https://repo.clojars.org/
>> Sending
>> com/github/atdixon/thurber/0.0.3-alpha8/thurber-0.0.3-alpha8.pom.asc (1k)
>> to https://repo.clojars.org/
>> Could not transfer metadata com.github.atdixon:thurber/maven-metadata.xml
>> from/to releases (https://repo.clojars.org): Failed to transfer file:
>> https://repo.clojars.org/com/github/atdixon/thurber/maven-metadata.xml.
>> Return code is: 400 , ReasonPhrase:Bad Request.
>> Failed to retrieve remote metadata
>> com.github.atdixon:thurber/maven-metadata.xml: Could not transfer metadata
>> com.github.atdixon:thurber/maven-metadata.xml from/to releases (
>> https://repo.clojars.org): Failed to transfer file:
>> https://repo.clojars.org/com/github/atdixon/thurber/maven-metadata.xml.
>> Return code is: 400 , ReasonPhrase:Bad Request.
>>
>> On Sunday, February 16, 2020 at 6:25:49 PM UTC-6, Aaron D. wrote:
>>>
>>> My gpg creds are as usual (and verified) and I'm deploying in standard
>>> fashion but my last attempt at lein deploy fails with 400/Bad Request at
>>> the very ened trying  to retrieve maven-metadata.xml -- is anyone / has
>>> anyone seen this? My last deploy was 10 days ago...
>>>
>>> The log to error:
>>>
>>> Created /code/thurber/target/thurber-0.0.3-alpha5-SNAPSHOT.jar
>>> Wrote /code/thurber/pom.xml
>>> Could not find metadata
>>> com.github.atdixon:thurber:0.0.3-alpha5-SNAPSHOT/maven-metadata.xml in
>>> snapshots (https://repo.clojars.org)
>>> Sending
>>> com/github/atdixon/thurber/0.0.3-alpha5-SNAPSHOT/thurber-0.0.3-alpha5-20200217.002121-1.jar
>>> (52k)
>>> to https://repo.clojars.org/
>>> Sending
>>> com/github/atdixon/thurber/0.0.3-alpha5-SNAPSHOT/thurber-0.0.3-alpha5-20200217.002121-1.pom
>>> (4k)
>>> to https://repo.clojars.org/
>>> Could not transfer metadata
>>> com.github.atdixon:thurber/maven-metadata.xml from/to snapshots (
>>> https://repo.clojars.org): Failed to transfer file:
>>> https://repo.clojars.org/com/github/atdixon/thurber/maven-metadata.xml.
>>> Return code is: 400 , ReasonPhrase:Bad Request.
>>> Failed to retrieve remote metadata
>>> com.github.atdixon:thurber/maven-metadata.xml: Could not transfer metadata
>>> com.github.atdixon:thurber/maven-metadata.xml from/to snapshots (
>>> https://repo.clojars.org): Failed to transfer file:
>>> https://repo.clojars.org/com/github/atdixon/thurber/maven-metadata.xml.
>>> Return code is: 400 , ReasonPhrase:Bad Request.
>>>
>>>
>> On Wednesday, February 19, 2020 at 7:25:13 PM UTC-6, Toby Crawley wrote:
>>>
>>> Also, what version of lein are you using? What is the output of `lein
>>> version`?
>>>
>>> On Wed, Feb 19, 2020 at 8:14 PM Toby Crawley 
>>> wrote:
>>> >
>>> > Howdy Aaron:
>>> >
>>> > We've h

[JOB] Software Engineer | Red Planet Labs | Fully distributed team

[Nathan Marz]

We're a well-funded startup building a new kind of software development 
tool that will radically change the economics of software development. 
We're backed by some amazing investors including Max Levchin, Naval 
Ravikant, and Alexis Ohanian.

Since our first round of hiring last year we've gotten the hang of 
operating as a fully distributed team and are now ready to grow the team 
further.

Our technology is entirely in Clojure, and it pushes the boundaries of 
what's possible with compilers, databases, and distributed systems. If 
you'd be interested in joining, please reach out!

*Website*: https://redplanetlabs.com/
*Blog post introducing company*: 
https://medium.com/red-planet-labs/introducing-red-planet-labs-2a0304a67312
*How we operate as a fully distributed team*: 
https://medium.com/red-planet-labs/why-fully-distributed-is-by-far-the-best-way-to-run-a-software-team-d99abfc0c700

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/clojure/305613bc-670a-4e75-b6af-4be1424f55af%40googlegroups.com.