Re: [JENKINS] Lucene-main-Linux (64bit/jdk-17.0.3) - Build # 35657 - Unstable!

[Vigya Sharma]

This should also get addressed by https://github.com/apache/lucene/pull/1012.
The PR fixes testWithExceptions failures for subclasses
of BasePointsFormatTestCase.

Vigya

On Sun, Jul 10, 2022 at 8:31 PM Policeman Jenkins Server <
jenk...@thetaphi.de> wrote:

> Build: https://jenkins.thetaphi.de/job/Lucene-main-Linux/35657/
> Java: 64bit/jdk-17.0.3 -XX:+UseCompressedOops -XX:+UseG1GC
>
> 1 tests failed.
> FAILED:
> org.apache.lucene.codecs.simpletext.TestSimpleTextPointsFormat.testWithExceptions
>
> Error Message:
> java.nio.file.NoSuchFileException:
> /home/jenkins/workspace/Lucene-main-Linux/lucene/codecs/build/tmp/tests-tmp/lucene.codecs.simpletext.TestSimpleTextPointsFormat_1F2E321F434B241B-001/tempDir-001/_0.dii
>
> Stack Trace:
> java.nio.file.NoSuchFileException:
> /home/jenkins/workspace/Lucene-main-Linux/lucene/codecs/build/tmp/tests-tmp/lucene.codecs.simpletext.TestSimpleTextPointsFormat_1F2E321F434B241B-001/tempDir-001/_0.dii
> at
> __randomizedtesting.SeedInfo.seed([1F2E321F434B241B:BD7DAE63CCC56BE1]:0)
> at
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
> at
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at
> java.base/sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:248)
> at
> java.base/sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:105)
> at
> org.apache.lucene.tests.mockfile.FilterFileSystemProvider.delete(FilterFileSystemProvider.java:134)
> at
> org.apache.lucene.tests.mockfile.FilterFileSystemProvider.delete(FilterFileSystemProvider.java:134)
> at
> org.apache.lucene.tests.mockfile.FilterFileSystemProvider.delete(FilterFileSystemProvider.java:134)
> at
> org.apache.lucene.tests.mockfile.FilterFileSystemProvider.delete(FilterFileSystemProvider.java:134)
> at
> org.apache.lucene.tests.mockfile.FilterFileSystemProvider.delete(FilterFileSystemProvider.java:134)
> at java.base/java.nio.file.Files.delete(Files.java:1152)
> at
> org.apache.lucene.store.FSDirectory.privateDeleteFile(FSDirectory.java:344)
> at
> org.apache.lucene.store.FSDirectory.deleteFile(FSDirectory.java:309)
> at
> org.apache.lucene.tests.store.MockDirectoryWrapper.deleteFile(MockDirectoryWrapper.java:651)
> at
> org.apache.lucene.store.LockValidatingDirectoryWrapper.deleteFile(LockValidatingDirectoryWrapper.java:37)
> at
> org.apache.lucene.index.IndexFileDeleter.deleteFile(IndexFileDeleter.java:763)
> at
> org.apache.lucene.index.IndexFileDeleter.deleteFiles(IndexFileDeleter.java:757)
> at
> org.apache.lucene.index.IndexFileDeleter.deleteNewFiles(IndexFileDeleter.java:729)
> at
> org.apache.lucene.index.IndexWriter.deleteNewFiles(IndexWriter.java:5763)
> at
> org.apache.lucene.index.IndexWriter.addIndexes(IndexWriter.java:3177)
> at
> org.apache.lucene.tests.index.RandomIndexWriter.addIndexes(RandomIndexWriter.java:334)
> at
> org.apache.lucene.tests.index.BasePointsFormatTestCase.switchIndex(BasePointsFormatTestCase.java:1195)
> at
> org.apache.lucene.tests.index.BasePointsFormatTestCase.verify(BasePointsFormatTestCase.java:797)
> at
> org.apache.lucene.tests.index.BasePointsFormatTestCase.testWithExceptions(BasePointsFormatTestCase.java:265)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1758)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:946)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:982)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:996)
> at
> org.apache.lucene.tests.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:44)
> at
> org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
> at
> org.apache.lucene.tests.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:45)
> at
> org.apache.lucene.tests.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:60)
> at
> org.apache.lucene.tests.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:44)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at
> 

Re: Missing tags for recent 8.x Solr releases

[Mike Drob]

+dev@solr
-dev@lucene to bcc

Hi Nemo,

The canonical location of our tags for the 8.x release line is
https://gitbox.apache.org/repos/asf?p=lucene-solr.git;a=tags

The tags for 9.x (and future) will all be at
https://gitbox.apache.org/repos/asf?p=solr.git;a=tags as you have found.
This is the unfortunate result of some continued split development.

We may be able to copy the 8.x tags to the solr repo as well, but I'm not
certain what our options are.

Mike

On Mon, Jul 11, 2022 at 12:10 AM Nemo  wrote:

>
> Hi,
>
> It appears that recent 8.x Solr releases (post 8.8.1) haven't been
> tagged on the Git repository[1]
>
> Is this an intentional release process change? Seeing as how the 9.0.0
> release was correctly tagged, could the missing releases be backtagged
> with the correct dates? The list of untagged releases is quite small:
>
> 8.8.2, 8.9.0, 8.10.0, 8.10.1
> 8.11.0, 8.11.1, 8.11.2
>
> Context: Writing this on behalf of the endoflife.date project, where we
> recently[2] added a endoflife.date/solr page. To track new releases
> automatically, we track tags on upstream repositories. In this case,
> tracking the repo would get us 8.8.1 as the latest release instead of
> 8.11.2. We could also track Docker images, but they seem to lag behind
> by a few days, and wouldn't give us good enough coverage.
>
> Please keep me in cc for replies.
>
> Thanks,
> Nemo
>
> [1]: https://gitbox.apache.org/repos/asf?p=solr.git;a=tags.
> [2]: https://github.com/endoflife-date/endoflife.date/pull/1389
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: Lucene 9.3.0 release

[Michael Sokolov]

I would like to see if we can get
https://issues.apache.org/jira/browse/LUCENE-10577 in. It is working
and gives nice gains, but there is some controversy about the API. If
we can't get it sorted out this week(?) it can certainly slip to the
next revision. I know that
https://issues.apache.org/jira/browse/LUCENE-10592 is also baking and
has a PR that seems to be progressing rapidly.

On Mon, Jul 11, 2022 at 10:03 AM Ignacio Vera  wrote:
>
> Hello!
>
> Lucene 9.2.0 was released around 2 months ago and we are accumulating a good 
> bunch of new features, optimizations and bug fixes. Would there be support 
> for releasing Lucene 9.3 soon?
>
> I am happy being the release manager. I did not see any issues marked 
> "blocker", but please let me know if there are any.
>
> Thanks,
>
>  Ignacio

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Lucene 9.3.0 release

[Alan Woodward]

+1, thanks Ignacio

> On 11 Jul 2022, at 15:02, Ignacio Vera  > wrote:
> 
> Hello!
> 
> Lucene 9.2.0 was released around 2 months ago and we are accumulating 
>  a good 
> bunch of new features, optimizations and bug fixes. Would there be support 
> for releasing Lucene 9.3 soon?
> 
> I am happy being the release manager. I did not see any issues marked 
> "blocker", but please let me know if there are any.
> 
> Thanks,
> 
>  Ignacio

Re: How to avoid double-emails on all git issue/PR updates?

[Michael McCandless]

EXCELLENT!  Thank you, I fixed this too in my settings.  Phew :)

Mike McCandless

http://blog.mikemccandless.com


On Mon, Jul 11, 2022 at 9:53 AM Uwe Schindler  wrote:

> Ah that explains why you get ALL messages twice. I recognized that after
> I sent my mail.
>
> Sorry,
>
> Uwe
>
> Am 11.07.2022 um 15:47 schrieb Michael Sokolov:
> > Oh! thank you - this will be a big help. I just went to
> > https://github.com/apache/lucene and then under "Watch" selected
> > "participating and mentions" instead of "all activity" (which I had
> > before).
> >
> > On Mon, Jul 11, 2022 at 5:46 AM Uwe Schindler  wrote:
> >> Hi,
> >>
> >> I fully agree with Adrien, because the mails land in different IMAP
> folders. This behaviour is also not different to JIRA, If I am watching an
> issue or opened/assigned it to me, i get direct mails!
> >>
> >> If I am actively working/watching on a PR or issue, i get the mail
> adressed directly to my main mail adress and they land in the inbox.
> Notifications about all issues of Lucene/Solr are filtered with Sieve and
> land in the Lucene-issues and Solr-issues folders. This folder is only
> checked quickly ("diagonally"), while mails adressed to me dircetly get
> higher importance as they land in INBOX.
> >>
> >> Theres also no way to prevent the duplicates if sent by different
> systems with different message-ids. My mail filtering only removes
> duplicates with same message ID (like mails going to multiple lists and
> CCed to myself; Dovecot has support to remove them from beginning).
> >>
> >> Uwe
> >>
> >> Am 11.07.2022 um 11:17 schrieb Adrien Grand:
> >>
> >> Hey Mike,
> >>
> >> I'm only subscribed to issues/PRs I'm participating in on GitHub, which
> I've found useful since I can filter these and be more reactive on them,
> while still having access to the entire stream of activity via issues@l.a.o.
> >>
> >> On Sun, Jul 10, 2022 at 2:27 PM Michael McCandless <
> luc...@mikemccandless.com> wrote:
> >>> Hi Team,
> >>>
> >>> Mike Sokolov mentioned this recently, making me realize it was not
> just me getting double-emails on comments on GitHub PRs/issues :)
> >>>
> >>> I think it happens because we are subscribed to notifications on
> Apache org repositories, so we get an email notification from GitHub (as an
> HTML email).  But then Apache mirrors these repos to its own Git instance,
> and that also sends notification emails (as plain text).
> >>>
> >>> Does anyone else see these duplicates because Mike S and I?  How do
> you avoid / fix it :)  Which one should we unsubscribe from?
> >>>
> >>> Mike McCandless
> >>>
> >>> http://blog.mikemccandless.com
> >>
> >>
> >> --
> >> Adrien
> >>
> >> --
> >> Uwe Schindler
> >> Achterdiek 19, D-28357 Bremen
> >> https://www.thetaphi.de
> >> eMail: u...@thetaphi.de
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: dev-h...@lucene.apache.org
> >
> --
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Lucene 9.3.0 release

[Ignacio Vera]

Hello!

Lucene 9.2.0 was released around 2 months ago and we are accumulating
 a good
bunch of new features, optimizations and bug fixes. Would there be support
for releasing Lucene 9.3 soon?

I am happy being the release manager. I did not see any issues marked
"blocker", but please let me know if there are any.

Thanks,

 Ignacio

Re: How to avoid double-emails on all git issue/PR updates?

[Uwe Schindler]

Ah that explains why you get ALL messages twice. I recognized that after 
I sent my mail.


Sorry,

Uwe

Am 11.07.2022 um 15:47 schrieb Michael Sokolov:

Oh! thank you - this will be a big help. I just went to
https://github.com/apache/lucene and then under "Watch" selected
"participating and mentions" instead of "all activity" (which I had
before).

On Mon, Jul 11, 2022 at 5:46 AM Uwe Schindler  wrote:

Hi,

I fully agree with Adrien, because the mails land in different IMAP folders. 
This behaviour is also not different to JIRA, If I am watching an issue or 
opened/assigned it to me, i get direct mails!

If I am actively working/watching on a PR or issue, i get the mail adressed directly to 
my main mail adress and they land in the inbox. Notifications about all issues of 
Lucene/Solr are filtered with Sieve and land in the Lucene-issues and Solr-issues 
folders. This folder is only checked quickly ("diagonally"), while mails 
adressed to me dircetly get higher importance as they land in INBOX.

Theres also no way to prevent the duplicates if sent by different systems with 
different message-ids. My mail filtering only removes duplicates with same 
message ID (like mails going to multiple lists and CCed to myself; Dovecot has 
support to remove them from beginning).

Uwe

Am 11.07.2022 um 11:17 schrieb Adrien Grand:

Hey Mike,

I'm only subscribed to issues/PRs I'm participating in on GitHub, which I've 
found useful since I can filter these and be more reactive on them, while still 
having access to the entire stream of activity via issues@l.a.o.

On Sun, Jul 10, 2022 at 2:27 PM Michael McCandless  
wrote:

Hi Team,

Mike Sokolov mentioned this recently, making me realize it was not just me 
getting double-emails on comments on GitHub PRs/issues :)

I think it happens because we are subscribed to notifications on Apache org 
repositories, so we get an email notification from GitHub (as an HTML email).  
But then Apache mirrors these repos to its own Git instance, and that also 
sends notification emails (as plain text).

Does anyone else see these duplicates because Mike S and I?  How do you avoid / 
fix it :)  Which one should we unsubscribe from?

Mike McCandless

http://blog.mikemccandless.com



--
Adrien

--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org


--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: How to avoid double-emails on all git issue/PR updates?

[Michael Sokolov]

Oh! thank you - this will be a big help. I just went to
https://github.com/apache/lucene and then under "Watch" selected
"participating and mentions" instead of "all activity" (which I had
before).

On Mon, Jul 11, 2022 at 5:46 AM Uwe Schindler  wrote:
>
> Hi,
>
> I fully agree with Adrien, because the mails land in different IMAP folders. 
> This behaviour is also not different to JIRA, If I am watching an issue or 
> opened/assigned it to me, i get direct mails!
>
> If I am actively working/watching on a PR or issue, i get the mail adressed 
> directly to my main mail adress and they land in the inbox. Notifications 
> about all issues of Lucene/Solr are filtered with Sieve and land in the 
> Lucene-issues and Solr-issues folders. This folder is only checked quickly 
> ("diagonally"), while mails adressed to me dircetly get higher importance as 
> they land in INBOX.
>
> Theres also no way to prevent the duplicates if sent by different systems 
> with different message-ids. My mail filtering only removes duplicates with 
> same message ID (like mails going to multiple lists and CCed to myself; 
> Dovecot has support to remove them from beginning).
>
> Uwe
>
> Am 11.07.2022 um 11:17 schrieb Adrien Grand:
>
> Hey Mike,
>
> I'm only subscribed to issues/PRs I'm participating in on GitHub, which I've 
> found useful since I can filter these and be more reactive on them, while 
> still having access to the entire stream of activity via issues@l.a.o.
>
> On Sun, Jul 10, 2022 at 2:27 PM Michael McCandless 
>  wrote:
>>
>> Hi Team,
>>
>> Mike Sokolov mentioned this recently, making me realize it was not just me 
>> getting double-emails on comments on GitHub PRs/issues :)
>>
>> I think it happens because we are subscribed to notifications on Apache org 
>> repositories, so we get an email notification from GitHub (as an HTML 
>> email).  But then Apache mirrors these repos to its own Git instance, and 
>> that also sends notification emails (as plain text).
>>
>> Does anyone else see these duplicates because Mike S and I?  How do you 
>> avoid / fix it :)  Which one should we unsubscribe from?
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>
>
>
> --
> Adrien
>
> --
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: u...@thetaphi.de

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: How to avoid double-emails on all git issue/PR updates?

[Uwe Schindler]

Hi,

I fully agree with Adrien, because the mails land in different IMAP 
folders. This behaviour is also not different to JIRA, If I am watching 
an issue or opened/assigned it to me, i get direct mails!


If I am actively working/watching on a PR or issue, i get the mail 
adressed directly to my main mail adress and they land in the inbox. 
Notifications about all issues of Lucene/Solr are filtered with Sieve 
and land in the Lucene-issues and Solr-issues folders. This folder is 
only checked quickly ("diagonally"), while mails adressed to me dircetly 
get higher importance as they land in INBOX.


Theres also no way to prevent the duplicates if sent by different 
systems with different message-ids. My mail filtering only removes 
duplicates with same message ID (like mails going to multiple lists and 
CCed to myself; Dovecot has support to remove them from beginning).


Uwe

Am 11.07.2022 um 11:17 schrieb Adrien Grand:

Hey Mike,

I'm only subscribed to issues/PRs I'm participating in on GitHub, 
which I've found useful since I can filter these and be more reactive 
on them, while still having access to the entire stream of activity 
via issues@l.a.o.


On Sun, Jul 10, 2022 at 2:27 PM Michael McCandless 
 wrote:


Hi Team,

Mike Sokolov mentioned this recently, making me realize it was not
just me getting double-emails on comments on GitHub PRs/issues :)

I think it happens because we are subscribed to notifications on
Apache org repositories, so we get an email notification from
GitHub (as an HTML email).  But then Apache mirrors these repos to
its own Git instance, and that also sends notification emails (as
plain text).

Does anyone else see these duplicates because Mike S and I?  How
do you avoid / fix it :)  Which one should we unsubscribe from?

Mike McCandless

http://blog.mikemccandless.com



--
Adrien


--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:u...@thetaphi.de

Re: How to avoid double-emails on all git issue/PR updates?

[Adrien Grand]

Hey Mike,

I'm only subscribed to issues/PRs I'm participating in on GitHub, which
I've found useful since I can filter these and be more reactive on them,
while still having access to the entire stream of activity via issues@l.a.o.

On Sun, Jul 10, 2022 at 2:27 PM Michael McCandless <
luc...@mikemccandless.com> wrote:

> Hi Team,
>
> Mike Sokolov mentioned this recently, making me realize it was not just me
> getting double-emails on comments on GitHub PRs/issues :)
>
> I think it happens because we are subscribed to notifications on Apache
> org repositories, so we get an email notification from GitHub (as an HTML
> email).  But then Apache mirrors these repos to its own Git instance, and
> that also sends notification emails (as plain text).
>
> Does anyone else see these duplicates because Mike S and I?  How do you
> avoid / fix it :)  Which one should we unsubscribe from?
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>


-- 
Adrien