Hi Qizhi,
I am moving your question to the Solr users list.
Le sam. 4 nov. 2023, 01:58, Qizhi Zheng a
écrit :
> Hello,
>
>
>
> I am trying to run the Solr Tutorial Exercise 1 Index Techproducts Data in
> Windows 10. I typed the exact same command following it link:
>
>
>
TL;DR, forcing non-committers to squash things is a good idea. Enforcing
through some measure for committers is a bad idea.
Since this thread is now in Robert's spam, I am guessing it won't have any
impact :). I do not think Robert is actively trying hurt the project in any
way. It seems to me
OK I opened https://github.com/eclipse-openj9/openj9/issues/18400 -- let's
see where that goes.
Uwe, should we upgrade to the latest OpenJ9 again maybe?
Mike McCandless
http://blog.mikemccandless.com
On Sat, Nov 4, 2023 at 12:25 PM Michael McCandless <
luc...@mikemccandless.com> wrote:
>
Likely J9 specific?
Mike McCandless
http://blog.mikemccandless.com
On Sat, Nov 4, 2023 at 11:34 AM Policeman Jenkins Server <
jenk...@thetaphi.de> wrote:
> Build: https://jenkins.thetaphi.de/job/Lucene-main-Linux/45409/
> Java: 64bit/openj9/jdk-17.0.5 -XX:-UseCompressedOops -Xgcpolicy:gencon
Hi Ben
Am 04.11.23 um 14:41 schrieb Benjamin Trent:
Hey Michael,
In short, it's being worked on :).
cool, thanks!
Could you point to the LinkedIN post?
Also, since (as noted) this is a previously decided issue, not sure why
this is a list email instead of a simple direct query to Robert seeking to
understand the specific case? No need to make a public discussion unless
it's a long term pattern, actually breaking something, or we want to change
Should we maybe stop testing J9? Reduce its frequency? So much noise ...
I know I can filter these out from my gmail box.
I will try opening an issue in the OpenJ9 GitHub repo:
https://github.com/eclipse-openj9/openj9/issues
Mike McCandless
http://blog.mikemccandless.com
On Fri, Nov 3,
Hey Michael,
In short, it's being worked on :).
Could you point to the LinkedIN post? Is Nils talking about the model
output quantized output or that their default output is easily compressible
because of how the embeddings are built?
I have done a bad job of linking back against that original
For what it's worth I basically agree with Michael Sokolov with the caveat
that I think it's sometimes useful to create a clean branch and re-pick the
changes if the merging has become complex just to make sure you are not
accidentally reverting anything vs what is on head unintentionally.
Maybe J9 specific?
Mike McCandless
http://blog.mikemccandless.com
On Sat, Nov 4, 2023 at 11:01 AM Policeman Jenkins Server <
jenk...@thetaphi.de> wrote:
> Build: https://jenkins.thetaphi.de/job/Lucene-main-Windows/13400/
> Java: 64bit/openj9/jdk-17.0.5 -XX:-UseCompressedOops -Xgcpolicy:gencon
Hi Uwe,
Thanks for your reply, comments inline.
> On 3 Nov 2023, at 13:11, Uwe Schindler wrote:
>
> Hi,
>
> I had another idea: Why not release main as 10.0.0 *NOW* and create
> branch_10x (with Java 17) minimum, stop working on 9.x, and move main branch
> to 21?
I see now that 9.x has a
Personally for me it's about how meaningful the commit messages (and
contents) are vs whether we use merge commits or not. If it;s a long series
of "fixed bug" "reformatted" "did stuff" "more stuff" "it finally works"
and so on ... that doesn't smell good to me, but you know we all have done
that
I didn't realize the community had decided squashing (rewriting history)
was our standard.
> Comparing histories between branches with git-bisect to find bugs is just
one example.
But if the bug was introduced in one of the N local commits the developer
had done, wouldn't that be helpful? You
Hi,
I just wanted to give your attention to the following discussion:
https://github.com/apache/lucene/pull/12737#issuecomment-1793426911
From my knowledge the Lucene (and Solr) community decided a while back
to disable merging and only allow squashig of PRs. Robert always did
this, but
example of a nanny state IMO, trying to dictate what git commands to
use, or what editor to use. Maybe this works for you in your corporate
hellholes, but I think some folks have a bit of a power issue, are
accustomed to dictacting this stuff to their employees and so on, but
this is open-source.
We all agree on using Java though, and using a specific version, and even
the style output from gradle tidy. Is that nanny state or community
consensus?
On Sat, Nov 4, 2023 at 7:29 AM Robert Muir wrote:
> example of a nanny state IMO, trying to dictate what git commands to
> use, or what editor
This isn't a community issue, it is me avoiding useless unnecessary
merge conflicts. Word "community" is invoked here to try to make it
out, like you can hold a vote about what git commands i should type on
my computer? You know that isn't gonna work. have some humility.
thread moved to spam.
On
Hi
If I understand correctly some devs are working on introducing
quantization for vector search or at least considering it
https://github.com/apache/lucene/issues/12497
Just being curious what is the status on this resp. is somebody working
on this actively?
It came to my mind, because
18 matches
Mail list logo
