ion and
> retry that request?
>
> On Thu, Feb 9, 2017 at 6:48 AM 'Matt Bossenbroek' via Clojure <
> clo...@googlegroups.com> wrote:
>
>> I'm using test.check to test a live service. Occasionally it gets a 503
>> from the service and spends hours trying t
, Daniel Compton (
daniel.compton.li...@gmail.com) wrote:
If the 503 is only returned by failures not relating to what you are
testing (e.g. load), then one option might be to catch the exception and
retry that request?
On Thu, Feb 9, 2017 at 6:48 AM 'Matt Bossenbroek' via Clojure
I'm using test.check to test a live service. Occasionally it gets a 503
from the service and spends hours trying to shrink the input & reproduce
the error.
Is there a way to limit the shrinking process to n iterations? Or disable
it entirely for some tests?
Is there a better approach for using
How about adding a state of Datomic survey? :)
-Matt
On Sunday, December 6, 2015 at 4:12 PM, Mars0i wrote:
>
>
> On Sunday, December 6, 2015 at 3:26:55 PM UTC-6, Lee wrote:
> >
> > On Dec 6, 2015, at 3:00 PM, Alex Miller > (javascript:)> wrote:
> >
> > > Almost all of the questions are o
We just released PigPen 0.3.1 with a couple of minor improvements:
Update cascading version to 2.7.0
Update nippy (for serialization) to 2.10.0 & tune performance
PigPen is map-reduce for Clojure, or distributed Clojure. You write idiomatic
Clojure code, we run it on thousands of machines usin
FWIW, We use edn (serialized with nippy [1]) in hadoop & it works very well for
us:
https://github.com/Netflix/PigPen
In some places we use maps for the expressiveness and in some we use vectors
for more performance.
Whatever I lose in raw performance I can trivially throw a few more boxes a
No complaints, so PigPen 0.3.0 is now officially released.
Enjoy!
-Matt
On Monday, May 11, 2015 at 8:40 AM, Matt Bossenbroek wrote:
> I'm excited to announce the release of PigPen v0.3.0, which now includes
> support for Cascading.
>
> PigPen is Map-Reduce for Clojure - you write idiomatic C
s)) (map f (rest s))
>
>
> holds onto the head via needing to keep the value of "s" around throughout
> the entire call to (f (first s)) in order to later make the call (map f (rest
> s)). In map2, the value of s is no longer needed by the time f is called.
>
&g
Ran into an interesting problem today. In short, this works:
(count (repeat 1e8 "stuff"))
But this doesn't:
(map count [(repeat 1e8 "stuff")])
To be fair, given sufficient memory, it would eventually complete. (If the
second example does work for you, change it to 1e10 or something higher).
e meantime.
-Matt
On Thursday, September 11, 2014 at 7:52 PM, Sunil S Nandihalli wrote:
> Thanks Mark and Matt, changing the version back to clojure version 1.6.0
> fixed it.
> Sunil
>
>
> On Fri, Sep 12, 2014 at 7:05 AM, 'Matt Bossenbroek' via Clojure
> mailto:c
Just saw this response - disregard the questions I asked you on the pigpen
support DL.
I'll pull in the new instaparse & get a new PigPen build out soonish (within a
day or two).
-Matt
On Thursday, September 11, 2014 at 6:28 PM, Mark Engelberg wrote:
> You're probably using Clojure 1.7.0 a
11 matches
Mail list logo
