Re: [DISCUSS] Solr 9.2 Release

[Mikhail Khludnev]

Hello, colleagues!
How can we triage https://issues.apache.org/jira/browse/SOLR-16681
Replacing uniqueKey field via fl doesn't work since 9.0?
I don't have an elegant solution. Will we just declare it as a known
bug/limitation?

On Fri, Feb 17, 2023 at 9:07 PM Houston Putman  wrote:

> Hey everyone,
>
> It's been a while since Solr 9.1 was released, and we have a ton of great
> things to show off in 9.2:
>
> - Jetty 10
> - JAX-RS
> - Lucene 9.5
>
> I volunteer to do the release starting in the week of March 6th, unless
> anyone else objects or wants to do it themselves.
>
> - Houston
>


-- 
Sincerely yours
Mikhail Khludnev
https://t.me/MUST_SEARCH
A caveat: Cyrillic!

Re: Renovate dependency update PRs enabled

[David Smiley]

I like the idea of a consolidated / organized list of dependency changes
per release in the CHANGES.txt.  If it could be automated -- awesome!

~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley


On Mon, Feb 27, 2023 at 11:33 AM Jan Høydahl  wrote:

> I agree that for most dep updates a committ message with PR link is enough.
> Or perhpaps we could write a script that release-wizard could run that
> adds a new section to CHANGES with all the dep updates in this release?
>
> Jan
>
> > 27. feb. 2023 kl. 13:08 skrev Ishan Chattopadhyaya <
> ichattopadhy...@gmail.com>:
> >
> >  (#)
> >
> > where  is the PR number is good enough. IntelliJ IDE understands
> this format and makes it a clickable link.
> >
> > On Mon, 27 Feb, 2023, 3:51 pm Jan Høydahl,  > wrote:
> >> Hi
> >>
> >> Current status is that solrbot has opened 25 Pull Requests with
> dependency upgrades. There are probably more, but we told the bot to rate
> limit on 25.
> >> If anyone wants to help triage which of these to include in the 9.2
> release, feel free to walk through the list and either approve, comment or
> push changes:
> >>
> >>
> >> Pull requests · apache/solr
> >> github.com
> >>  Pull requests ·
> apache/solr 
> >> github.com 
> >>
> >> We also have to decide how to handle CHANGES entries for bot updates.
> My thinking is that many minor/patch upgrades may not need a changes line,
> while issues that also require some work in Solr code may need one, and
> that can be added in the PR branch by the committer.
> >>
> >> Many of these won't need a JIRA issue either, so this could be a good
> time to start adding Github PR numbers to CHANGES.txt. I think we already
> support these formats:
> >>
> >> * GH#123: Update foo to 1.2.3
> >> * GITHUB#123: Update foo to 1.2.3
> >> * GH-123: Update foo to 1.2.3
> >> * GITHUB-123: Update foo to 1.2.3
> >> * github pull request 123: Update foo to 1.2.3
> >>
> >> Any thoughts?
> >>
> >> Jan
> >>
> >>> 24. feb. 2023 kl. 10:34 skrev Jan Høydahl  >:
> >>>
> >>> Hi all devs,
> >>>
> >>> We are testing dependabot-style PRs for dependency updates.
> >>> So be prepared to see new PRs opened by a bot user called "solrbot"
> (which I'm maintaining).
> >>> Initially there will be quite a few of these, and after that a
> once-a-week batch of new PRs.
> >>>
> >>> See
> https://github.com/apache/solr/blob/main/dev-docs/dependency-upgrades.adoc
> for some dev-docs about the feature.
> >>>
> >>> Hoping this will be a positive contribution to the project's
> dependency health.
> >>> Please bear over with us as we tune the schedule and sensitivity of
> the bot, so it's not too noisy :)
> >>>
> >>> Jan
> >>
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> > For additional commands, e-mail: dev-h...@solr.apache.org
>
>

Re: [DISCUSS] Community Virtual Meetup, March 2023

[Noble Paul]

Thanks Jason
I have no objections to March 8


On Wed, Mar 1, 2023 at 6:48 AM Jason Gerlowski 
wrote:

> > but what does it mean to host a Virtual meetup?
>
> Mostly it's just handling the administrative tasks that help the
> meetup happen and go smoothly: scheduling the video call, spreading
> the word in various places, creating a Confluence page for folks to
> propose their discussion topics, etc.  Maybe I'll "host" this one, and
> then I can put together a checklist or something so it's easier for
> other volunteers going forward.
>
> > To be clear "2 hrs later"
>
> Sure, works for me.  I choose noon ET last time because that was 5pm
> in the UK which still seemed somewhat do-able.  But I don't think
> anyone out that way logged on last time.  So let's do the shift you
> suggested this time and see how that goes.
>
> In terms of the date, let's aim for March 8th?  I'll put together the
> Confluence page shortly for folks to add their potential topics to.
>
> Jason
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org
> For additional commands, e-mail: dev-h...@solr.apache.org
>
>

-- 
-
Noble Paul

Re: [DISCUSS] Community Virtual Meetup, March 2023

[Jason Gerlowski]

> but what does it mean to host a Virtual meetup?

Mostly it's just handling the administrative tasks that help the
meetup happen and go smoothly: scheduling the video call, spreading
the word in various places, creating a Confluence page for folks to
propose their discussion topics, etc.  Maybe I'll "host" this one, and
then I can put together a checklist or something so it's easier for
other volunteers going forward.

> To be clear "2 hrs later"

Sure, works for me.  I choose noon ET last time because that was 5pm
in the UK which still seemed somewhat do-able.  But I don't think
anyone out that way logged on last time.  So let's do the shift you
suggested this time and see how that goes.

In terms of the date, let's aim for March 8th?  I'll put together the
Confluence page shortly for folks to add their potential topics to.

Jason

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

Re: [JENKINS-EA] Solr-main-Windows (64bit/hotspot/jdk-21-ea+9) - Build # 2404 - Unstable!

[Kevin Risden]

Commented on https://issues.apache.org/jira/browse/SOLR-16608 about these
failures since they are brand new from the recent commit it looks like.

Kevin Risden


On Tue, Feb 28, 2023 at 11:17 AM Policeman Jenkins Server <
jenk...@thetaphi.de> wrote:

> Build: https://jenkins.thetaphi.de/job/Solr-main-Windows/2404/
> Java: 64bit/hotspot/jdk-21-ea+9 -XX:-UseCompressedOops -XX:+UseG1GC
>
> 2 tests failed.
> FAILED:  org.apache.solr.cloud.ZkCLITest.testGetCompressed
>
> Error Message:
> array lengths differed, expected.length=12 actual.length=13; arrays first
> differed at element [12]; expected: but was:<13>
>
> Stack Trace:
> array lengths differed, expected.length=12 actual.length=13; arrays first
> differed at element [12]; expected: but was:<13>
> at
> __randomizedtesting.SeedInfo.seed([99554258B211B0A7:D587AE20C0E2B2B8]:0)
> at
> org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:89)
> at
> org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:28)
> at org.junit.Assert.internalArrayEquals(Assert.java:534)
> at org.junit.Assert.assertArrayEquals(Assert.java:343)
> at org.junit.Assert.assertArrayEquals(Assert.java:354)
> at
> org.apache.solr.cloud.ZkCLITest.testGetCompressed(ZkCLITest.java:465)
> at
> java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> at java.base/java.lang.reflect.Method.invoke(Method.java:578)
> 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
> com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:80)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> 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
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at
> com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:390)
> at
> com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:843)
> at
> com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:490)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:955)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:840)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:891)
> at
> com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:902)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at
> org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
> at
> org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
> at
> com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:80)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at
> org.apache.lucene.tests.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:43)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
> at
> org.apache.lucene.tests.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:38)
> at
> com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
> at
> com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
> at
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:3

Re: [DISCUSS] Community Virtual Meetup, March 2023

[Noble Paul]

To be clear "2 hrs later"

On Tue, Feb 28, 2023 at 10:37 PM Noble Paul  wrote:

> @Jason is it possible to keep the time 2 hours ahead?
>
> On Tue, Feb 28, 2023 at 6:32 PM Ishan Chattopadhyaya <
> ichattopadhy...@gmail.com> wrote:
>
>> +1, thanks Dave!
>>
>> On Tue, Feb 28, 2023 at 10:24 AM Dave 
>> wrote:
>>
>> > I had a solr presentation with ml I was ready to submit pre COVID. Would
>> > love to show people what I made, but I also have a tendency to mumble or
>> > miss words when I get excited about something.  If anyone is interested
>> in
>> > helping me communicate what it is with some dialogue I’d love to
>> contribute
>> > to the meeting
>> >
>> > > On Feb 27, 2023, at 11:46 PM, Ishan Chattopadhyaya <
>> > ichattopadhy...@gmail.com> wrote:
>> > >
>> >
>>
>
>
> --
> -
> Noble Paul
>


-- 
-
Noble Paul

Re: [DISCUSS] Community Virtual Meetup, March 2023

[Noble Paul]

@Jason is it possible to keep the time 2 hours ahead?

On Tue, Feb 28, 2023 at 6:32 PM Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> wrote:

> +1, thanks Dave!
>
> On Tue, Feb 28, 2023 at 10:24 AM Dave 
> wrote:
>
> > I had a solr presentation with ml I was ready to submit pre COVID. Would
> > love to show people what I made, but I also have a tendency to mumble or
> > miss words when I get excited about something.  If anyone is interested
> in
> > helping me communicate what it is with some dialogue I’d love to
> contribute
> > to the meeting
> >
> > > On Feb 27, 2023, at 11:46 PM, Ishan Chattopadhyaya <
> > ichattopadhy...@gmail.com> wrote:
> > >
> >
>


-- 
-
Noble Paul