+1 (non-binding)
SUCCESS! [1:05:42.202068]
Xugang
https://www.amazingkoala.com.cn/
Michael McCandless 于2023年9月26日周二 10:10写道：
> +1
>
> SUCCESS! [0:21:40.221538]
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Mon, Sep 25, 2023 at 7:01 AM Julie Tibshirani
> wrote:
>
>> +1
>>
+1
SUCCESS! [0:21:40.221538]
Mike McCandless
http://blog.mikemccandless.com
On Mon, Sep 25, 2023 at 7:01 AM Julie Tibshirani
wrote:
> +1
>
> SUCCESS! [0:41:00.311710]
>
> Julie
>
> On Mon, Sep 25, 2023 at 9:38 AM Anshum Gupta
> wrote:
>
>> +1
>>
>> Smoke tester is happy!
>>
>> SUCCESS!
+1
SUCCESS! [0:41:00.311710]
Julie
On Mon, Sep 25, 2023 at 9:38 AM Anshum Gupta wrote:
> +1
>
> Smoke tester is happy!
>
> SUCCESS! [0:46:49.090567]
>
> On Thu, Sep 21, 2023 at 10:49 PM Patrick Zhai wrote:
>
>> Please vote for release candidate 1 for Lucene 9.8.0
>>
>> The artifacts can be
+1
Smoke tester is happy!
SUCCESS! [0:46:49.090567]
On Thu, Sep 21, 2023 at 10:49 PM Patrick Zhai wrote:
> Please vote for release candidate 1 for Lucene 9.8.0
>
> The artifacts can be downloaded from:
>
>
thanks for the detailed info, folks. I'll see if I can understand why
I may have been running an old instance of that agent. The host I was
running on was created recently.
On Mon, Sep 25, 2023 at 6:09 AM Chris Hegarty
wrote:
>
> Hi,
>
> 2>at Log4jHotPatch.asmVersion(Log4jHotPatch.java:71)
I opened https://github.com/apache/lucene/pull/12588 as one way to address
this.
On Mon, Sep 25, 2023 at 2:07 PM Luca Cavanna wrote:
> This is caused by https://github.com/apache/lucene/pull/12183 , yet I
> don't think there is anything wrong with the PR itself.
>
> Looking at the test and
This is caused by https://github.com/apache/lucene/pull/12183 , yet I don't
think there is anything wrong with the PR itself.
Looking at the test and QueryUtils, we create a new searcher for each leaf
reader, and each searcher gets a separate executor. That would be ok as
long as the executors
Hi,
>> 2>at Log4jHotPatch.asmVersion(Log4jHotPatch.java:71)
This coming from Amazon’s Log4Shell hot patch [1], which I believe was deployed
by default on many (all?) JVM’s running on Amazon instances. Well… that was
almost 2yrs ago, not sure why it’s still showing up in some places now -
Hi,
as Lucene does not use Log4j, it is unclear why it wants to patch
anything. The problem in indeed caused by SecurityManager which is
enabled for running Lucene tests. Actually it detects that something
tries to access some internals of ASM, not sure what it exactly does.
The "injected"
