Mark Robert Miller

Thanks for taking a look. I have a n update I'll push I'll push tomorrow.

A couple of those are extra lines that came in when I merged to a clean repo (test policy and s3 build.gradle I believe). I'll get the follow up pushed...

That was a bit more effort than expected, but updated jetty from 10.0.7 to 10.0.8. That removes the need for the security policy read permission for "/". Rebased to latest...

> I don't think we need this - tried running tests locally without it and using S3_MOCK_RULE to build the client directly and things seemed fine. I actually took things...

Okay, I had missed in the patch you passed me how you proposed dealing with the toolchain dep issue - just using that instead of servlet-api - that seems fine...

I can put up a more recent rebase. The main reason this has sat around is a small but prominent back compat issue. We ship existing jetty.xml config with the...

I don’t know that modifying jetty.xml is that common. If the only case you were affected is if you had, I would just say release note it. The problem is,...

I’m happy to treat jetty.xml as an implantation detail, really only concerned with the semi odd shock of not being able to start up with an existing, unmodified file. If...

No frills type output possibilities. ``` Result "org.apache.lucene.bench.search.SearchPerf.term": 1163.320 ±(99.9%) 262.404 ops/s [Average] (min, avg, max) = (1090.710, 1163.320, 1242.755), stdev = 68.146 CI (99.9%): [900.915, 1425.724] (assumes normal distribution)...

Now we can pull some good clean perfasm: Result "org.apache.lucene.bench.search.SearchPerf.orHighHigh": 46.523 ±(99.9%) 2.531 ops/s [Average] (min, avg, max) = (45.641, 46.523, 47.235), stdev = 0.657 CI (99.9%): [43.991, 49.054] (assumes...