Re: [ANN] Cognitect Labs' aws-api 0.8.335

Unfortunately, 0.8.335 introduced a bug in the iam client. Fortunately, release 0.8.342 fixes it, so use that instead! On Friday, July 5, 2019 at 2:37:40 PM UTC-5, David Chelimsky wrote: > > Cognitect Labs' aws-api 0.8.335 is now available! > > CHANGES > >- use clojure.data.xml instead of clo

[ANN] Cognitect Labs' aws-api 0.8.342

Cognitect Labs' aws-api 0.8.342 is now available! CHANGES - skip whitespace when reading XML (fixes #85 ) README: https://github.com/cognitect-labs/aws-api/ API Docs: https://cognitect-labs.github.io/aws-api/ Changelog: https://github.c

Re: [ANN] Cognitect Labs' aws-api 0.8.335

David, what's wrong with clojure.xml that pushed cognitect-labs/aws-api to try another library, and is there a Jira issue for it? > > -- 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 t

Re: core.async: Unbound channels

"Effective" is in the eye of the beholder. The 1024 limit helps surface bugs wherein more than a thousand threads are blocked for lack of a certain channel's buffer space. But the 1024 limit does not pertain if 1 thread would like to do thousands of puts for which there is no buffer space. In

PSA: A slight tweak to "concat"

There's activity on a ticket in Jira to fix a quirk of "concat" that dates back to a commit by chouser in 2009! It's subtle because the title of CLJ-2523 is "lazy-cat can cause StackOverflowError with more than 2 arguments", which describes a sy

Re: [ANN] Cognitect Labs' aws-api 0.8.335

clojure.xml is a ns built into Clojure core that dates from very early days of Clojure. At a later point, it almost certainly would have been in clojure-contrib or a separate library. It is not a good choice for anything more than one-off code. In particular, it will cause reflection/illegal acc

Re: [ANN] Cognitect Labs' aws-api 0.8.335

Unfortunately, 0.8.335 introduced two bugs! One in the iam client, and one in pretty much everything because the pom.xml didn't get updated with the new deps. Please use 0.8.345, which fixes both issues. On Saturday, July 6, 2019 at 6:11:09 AM UTC-5, David Chelimsky wrote: > > Unfortunately, 0.

[ANN] Cognitect Labs' aws-api 0.8.345

Cognitect Labs' aws-api 0.8.345 is now available! CHANGES - Update pom.xml with same deps as deps.edn #86 README: https://github.com/cognitect-labs/aws-api/ API Docs: https://cognitect-labs.github.io/aws-api/ Changelog: https://github.

Re: [ANN] Cognitect Labs' aws-api 0.8.342

One more time Use 0.8.345 instead, please. On Saturday, July 6, 2019 at 6:14:16 AM UTC-5, David Chelimsky wrote: > > Cognitect Labs' aws-api 0.8.342 is now available! > > CHANGES > >- skip whitespace when reading XML (fixes #85 >)

Re: [ANN] Cognitect Labs' aws-api 0.8.345

Since installing aws-api 0.8.345, I am getting the following error: ```Unable to resolve symbol: requiring-resolve in this context, compiling:(cognitect/aws/http.clj:63:10)``` On Saturday, July 6, 2019 at 12:14:59 PM UTC-7, David Chelimsky wrote: > > Cognitect Labs' aws-api 0.8.345 is now availa

RE: Re: [ANN] Cognitect Labs' aws-api 0.8.345

That’s new in Clojure 1.10. I thought Cognitect AWS stuff required 1.10 from the get-go but I assume you had it working on 1.9? Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEANAn Architect's View -- http://corfield.org/"If you're not annoying somebody, you're not really alive."-- Margaret Atwood F

Re: [ANN] Cognitect Labs' aws-api 0.8.345

Yes, I did. It’s working again with aws-api 0.8.305 > On Jul 6, 2019, at 2:39 PM, wrote: > > That’s new in Clojure 1.10. I thought Cognitect AWS stuff required 1.10 from > the get-go but I assume you had it working on 1.9? > > Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN > An Architect'