Re: Clojure 1.10 "Illegal Reflective Access Operation"

[Vitex Software]

Todays warning:


(defn fix-fields
  "Only Fields branch"
  []
  (:content (-> (clojure.zip/xml-zip (xml/parse 
"specs/RHUB_v2.8_QuickFIX.xml"))
zip/down
zip/right
zip/right
zip/right
zip/right
zip/node))
  )

(defn fix-fields->format [rec]
  {:tag (-> rec :attrs :number Long/parseLong)
   :name(-> rec :attrs :name)
   :type(-> rec :attrs :type)
   :keyword (csk/->kebab-case (-> rec :attrs :name))
   :values  (-> rec :content :enum)
   })


(def fix-fields-reindexed (->> (fix-fields) (map fix-fields->format)))

=> 

ARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
clojure.lang.InjectedInvoker/0x7f3ca00b4c40 
(file:/home/vitex/.m2/repository/org/clojure/clojure/1.10.1/clojure-1.10.1.jar) 
to method 
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(org.xml.sax.InputSource,org.xml.sax.HandlerBase)
WARNING: Please consider reporting this to the maintainers of 
clojure.lang.InjectedInvoker/0x7f3ca00b4c40
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release

-- 
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/928ac222-c7b8-48fe-ae1e-4f6d7207ae0e%40googlegroups.com.

Re: A controversial call to bump libraries from 0.x to 1.0

[Alex Miller]

I think you are misinterpreting what people believe the 0.x to 1.x means. 
In the wide world of semver, 0.x indicates "unstable" and 1.x indicates 
"first stable"- you're conflating that special case with a general n.x to 
n+1.x which is interpreted as "breaking change". (See https://semver.org/ 
#4 and #8)

In this case, these contrib libraries at least are already stable and have 
been so for years. Moving from 0.x to 1.x is recognition of that for those 
with the above interpretation.


On Tuesday, February 18, 2020 at 7:46:20 PM UTC-6, Matching Socks wrote:
>
> Dear August Forum:  Today I noticed a new post on "Inside Clojure" 
> https://insideclojure.org/2020/02/18/lib-version/ , which says, after 
> some thoughtful justification, "we have lots of libraries in the Clojure 
> ecosystem that have been around for many years, are widely used, have 
> stable APIs, and yet are 0.x version. It’s silly for that to be (falsely) 
> indicating to people not to use them, so I have asked Clojure contrib 
> library owners to more actively bump up their library versions."
>
> A 0.x version number is a badge of honor; earned, not bestown.  It is one 
> of the things that makes Clojure stand out.  Let's not throw it away.
>
> If 0.x's -- at org.clojure and beyond -- renumbered themselves as 1.x's, 
> it would set off years of annoying aftershocks as a massive 
> dependency-update churn rippled far and wide.
>
> And still, people who don't like quiet would complain, "Clojure is fine, 
> but most of the libraries never got past 1.0."  You can't outrun that mob.  
> Stand firm.  If complaints about stasis are going to happen, better they 
> happened to 0.x than 1.x.  You can at least defend 0.x on principle.
>
> In short, I hope maintainers will defer the 0.x to 1.x transition until 
> they must commit a breaking or major change.
>

-- 
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/625b0cac-d408-45aa-b833-78cff7edab3a%40googlegroups.com.

Re: Clojure 1.10 "Illegal Reflective Access Operation"

[Alex Miller]

I believe this has already been discussed in this same thread, but to 
rehash.

More info on what this warning means: 
https://clojure.org/guides/faq#illegal_access

To diagnose the cause, you can use --illegal-access=debug to get better 
info about the cause. Here I assume it's in xml/parse, but you haven't 
provided enough info to know what exactly xml is aliasing here. One likely 
candidate is clojure.xml and indeed clojure.xml/parse is reflective by 
design. You should consider that function deprecated - it does not present 
a full range of xml parsing options in the modern world and you should use 
the contrib lib org.clojure/data.xml instead (which does not have this 
issue). 

On Wednesday, February 19, 2020 at 8:26:49 AM UTC-6, Vitex Software wrote:
>
> Todays warning:
>
>
> (defn fix-fields
>   "Only Fields branch"
>   []
>   (:content (-> (clojure.zip/xml-zip (xml/parse 
> "specs/RHUB_v2.8_QuickFIX.xml"))
> zip/down
> zip/right
> zip/right
> zip/right
> zip/right
> zip/node))
>   )
>
> (defn fix-fields->format [rec]
>   {:tag (-> rec :attrs :number Long/parseLong)
>:name(-> rec :attrs :name)
>:type(-> rec :attrs :type)
>:keyword (csk/->kebab-case (-> rec :attrs :name))
>:values  (-> rec :content :enum)
>})
>
>
> (def fix-fields-reindexed (->> (fix-fields) (map fix-fields->format)))
>
> => 
>
> ARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> clojure.lang.InjectedInvoker/0x7f3ca00b4c40 
> (file:/home/vitex/.m2/repository/org/clojure/clojure/1.10.1/clojure-1.10.1.jar)
>  
> to method 
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(org.xml.sax.InputSource,org.xml.sax.HandlerBase)
> WARNING: Please consider reporting this to the maintainers of 
> clojure.lang.InjectedInvoker/0x7f3ca00b4c40
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
>
>

-- 
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/cd43204d-cbd2-488e-95dc-26a392f991bc%40googlegroups.com.

DKIM signing

[Brjánn Ljótsson]

Hi,

Does anyone know of a email DKIM signing implementation in Clojure?

Best wishes,
Brjánn Ljótsson
Karolinska Institutet
Sweden

-- 
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/33133ae9-de72-4cb8-a9f3-26feabb5d20c%40googlegroups.com.

ANN: jedi-time 0.2.1

[dimitris]

Hi folks,

Third time is a charm they say ... :)

After spending a bit more time with REBL and my specs, I realised that 
navigation with the former can be made more intuitive, and the latter 
should be simpler. Therefore, I (slightly) changed the data-model again, 
and I think have finally found an approach that is both intuitive, 
consistent and significantly simplifies the specs (there is a single 
spec file now). In fact, I must admit that I kinda see the appeal of 
REBL now :)


I truly believe that this is the data-model I will be sticking with 
going forward, but as always I'm open to feedback. See the README/INTRO 
[1] for more.


Kind regards,

Dimitris

[1]: https://github.com/jimpil/jedi-time


--
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/eac91e8f-6a78-b84b-d473-af11ad8da93b%40gmail.com.

[ANN] superlifter - DataLoader for Clojure

[Oliver Hine]

Hi everyone,

I am pleased to announce the first release of superlifter 
.

Superlifter is an implementation of DataLoader 
 for Clojure.

To quote from the DataLoader readme:

DataLoader allows you to decouple unrelated parts of your application 
without sacrificing the performance of batch data-loading. While the loader 
presents an API that loads individual values, all concurrent requests will 
be coalesced and presented to your batch loading function. This allows your 
application to safely distribute data fetching requirements throughout your 
application and maintain minimal outgoing data requests.

Superlifter uses Urania , a remote data 
access library for Clojure/script inspired by Haxl 
 which in turn inspired DataLoader. 
Urania allows batching of similar fetches and deduplication via caching of 
identical fetches.

Superlifter adds smooth integration with libraries like lacinia 
, where GraphQL resolvers are run 
independently and must return data (or promises of data), leading to 1+n 
problems which can otherwise only be resolved by prefetching which 
complicates code.
There is a readme and an example project for a Lacinia GraphQL server at 
the repo on Github https://github.com/oliyh/superlifter

Feedback appreciated, as always, here or on Github.

Cheers,
Oliy

-- 
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/2cf044bf-1707-4ce8-89cd-a7f6fcb46d98%40googlegroups.com.

Re: Clojars deployment failing

[Toby Crawley]

Howdy Aaron:

We've had a report from another user on Slack of this same issue, but
I haven't been able to recreate it.

What do you mean by "I disabled :checksum checking for clojars"?

What version of java are you using? What is the output of java -version?

Thanks!
- Toby

--
"Arrogance is quoting yourself." - Toby Crawley
"Ignorance is quoting others." - Aaron T. Dixon

On Sun, Feb 16, 2020 at 7:37 PM Aaron Dixon  wrote:
>
> update, I disabled :checksum checking for clojars and was able to get a 
> release thru.
>
> On Sun, Feb 16, 2020 at 6:26 PM 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.
>>
>> --
>> 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 a topic in the 
>> Google Groups "Clojure" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/clojure/0xEg6HewEgM/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> clojure+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/clojure/f4773905-5ded-4da1-ba5e-872b0fc925d4%40googlegroups.com.
>
> --
> 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/CAFahMUqiPBxHVbZeQGw4B1iHQQyvj7Z2hLb75ejfKf4VmbJpJg%40mail.gmail.com.

-- 
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/CAA3HuyY1CmUX1iUcaCZQYNBFtZZtA9TVLMpBGKuT1egPyQvqmg%40mail.gmail.com.

Re: Clojars deployment failing

[Toby Crawley]

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 had a report from another user on Slack of this same issue, but
> I haven't been able to recreate it.
>
> What do you mean by "I disabled :checksum checking for clojars"?
>
> What version of java are you using? What is the output of java -version?
>
> Thanks!
> - Toby
>
> --
> "Arrogance is quoting yourself." - Toby Crawley
> "Ignorance is quoting others." - Aaron T. Dixon
>
> On Sun, Feb 16, 2020 at 7:37 PM Aaron Dixon  wrote:
> >
> > update, I disabled :checksum checking for clojars and was able to get a 
> > release thru.
> >
> > On Sun, Feb 16, 2020 at 6:26 PM 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.
> >>
> >> --
> >> 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 a topic in the 
> >> Google Groups "Clojure" group.
> >> To unsubscribe from this topic, visit 
> >> https://groups.google.com/d/topic/clojure/0xEg6HewEgM/unsubscribe.
> >> To unsubscribe from this group and all its topics, send an email to 
> >> clojure+unsubscr...@googlegroups.com.
> >> To view this discussion on the web visit 
> >> https://groups.google.com/d/msgid/clojure/f4773905-5ded-4da1-ba5e-872b0fc925d4%40googlegroups.com.
> >
> > --
> > 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/CAFahMUqiPBxHVbZeQGw4B1iHQQyvj7Z2hLb75ejfKf4VmbJpJg%40mail.gmail.com.

-- 
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/CAA3Huya9baOU-2vXFTmMMaxDNscKYnZsRtTuygRhTAw_U7za4Q%40mail.gmail.com.

Re: Clojars deployment failing

[Aaron D.]

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 had a report from another user on Slack of this same issue, but 
> > I haven't been able to recreate it. 
> > 
> > What do you mean by "I disabled :checksum checking for clojars"? 
> > 
> > What version of java are you using? What is the output of java -version? 
> > 
> > Thanks! 
> > - Toby 
> > 
> > -- 
> > "Arrogance is quoting yourself." - Toby Crawley 
> > "Ignorance is quoting others." - Aaron T. Dixon 
> > 
> > On Sun, Feb 16, 2020 at 7:37 PM Aaron Dixon  > wrote: 
> > > 
> > > update, I disabled :checksum checking for clojars and was

Re: Clojars deployment failing

[Aaron D.]

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 had a report from another user on Slack of this same issue, but 
>> > I haven't been able to recreate it. 
>> > 
>> > What do you mean by "I disabled :checksum checking for clojars