from:"Vera"

Re: [spectre] [CAS] 2024 Member's Exhibition Opening & Reception - 26 June

2024-05-21 Thread Vera Frenkel via SPECTRE

Hello Paul,
Tried to register, but was asked for a code that I couldn’t find.

Vera

On Tue, May 21, 2024 at 4:00 PM Paul Brown via SPECTRE <
spectre@mikrolisten.de> wrote:

>
> The Computer Arts Society’s 2024 series of events continues
>
> *2024 CAS Member’s Exhibition*
> Opening Reception and talks by Participating Artists
>
>
> 19:00 BST, Wednesday 26 June 2024 In Person and via Zoom
> Other time zones here:  https://www.timeanddate.com
>
> The event will be held in person at the BCS London offices and via Zoom.
> BCS, The Chartered Institute for IT
> Ground Floor
> 25 Copthall Avenue
> <https://www.google.com/maps/search/25+Copthall+Avenue+London,+EC2R+7BP,+UK?entry=gmail=g>
> London, EC2R 7BP, UK
> <https://www.google.com/maps/search/25+Copthall+Avenue+London,+EC2R+7BP,+UK?entry=gmail=g>
> Directions here:
> https://www.bcs.org/about-us/our-london-office-and-event-venue/
>
> This new exhibition at the CAS gallery space at the BCS London HQ shows 20
> recent works by our members selected from entries submitted for
> review.  Curated by Sean Clark and selected by a panel including Catherine
> Mason, Nick Lambert, Geoff Davis and Paul Brown.
>
> Speakers to be announced.  Moderator: Sean Clark
>
> The event will be recorded and uploaded to the CAS YouTube Channel.
>
> This event is open to the public and is free but you must book your place
> for both in-person and zoom attendance here:
> https://computerartssociety26062024.eventbrite.co.uk/
>
> __
>
> Our next meeting is the *EVA 2024* Conference - Monday 8 - Friday 12 July
> 2024
>
> You can see our future programme here:
> https://computer-arts-society.com/events/index.html
>
> __
> SPECTRE list for media culture in Deep Europe
> Info, archive and help:
> http://post.in-mind.de/cgi-bin/mailman/listinfo/spectre
>
__
SPECTRE list for media culture in Deep Europe
Info, archive and help:
http://post.in-mind.de/cgi-bin/mailman/listinfo/spectre

Re: pls help - basic access

2024-05-03 Thread Fernando Silva Vera

Any update?
I need to deliver a development 

If you need any type of information, I am at your disposal.

El jueves, 2 de mayo de 2024 a las 5:36:24 UTC+2, Google Ads API Forum 
Advisor escribió:

> Hi,
>
> Thank you for reaching out to the Google Ads API support team.
>
> I understand that you have applied for Basic access to the Google Ads API. 
> Since the access requests are handled by the Google Ads API Compliance 
> team, we are transferring the case to the Ads API Compliance team.
>
> @Compliance team, please confirm if you are able to assist in the below 
> access request.
>
> Summary: 
>
> The user has applied for Basic access to the Google Ads API with the below 
> details. 
>
>
>
>- Google Ads Manager Account (MCC) ID: 904-417-4760 
>
>
>- Case ID: The user did not receive case ID 
>
> Do reach out to the Google Ads API 
>  support team 
> for any queries related to the API.
>
>   
> This message is in relation to case 
> "ref:!00D1U01174p.!5004Q02tIr84:ref" (ADR-00233376)
>
> Thanks,
>   
> [image: Google Logo] Google Ads API Team 
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/d9549b2e-53ec-4b39-81af-5f9275ef1596n%40googlegroups.com.

pls help - Basic Access 

2024-05-01 Thread Fernando Silva Vera

Hello

I have a development for a client and I need to deliver it.
With Facebook ads and Tiktok ads, obtaining access to production has been 
very simple. I don't understand why Google is so slow. I've been waiting 
for 1 month and my client is rushing me.

These are my data


   - Google Ads Manager Account (MCC) ID : 904-417-4760


   - Cases ID : No case Id


   - Access level : Basic access 


Please a little help and get access managed quickly 

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/e04d19fe-d525-47f1-9e0a-8388a61055b6n%40googlegroups.com.

Requesting convert basic access token to standard access token

2024-04-25 Thread Fernando Silva Vera

I have been waiting for months to be approved for access at the basic 
level, can you help me?

I'm developing an app and I need to have access to test with production 
data, please help, I've been stuck with this for months and I can't get an 
answer

Here is the information:
*Google Ads Manager Account ID (MCC):* 904-417-4760
*Access level:* Basic access requested
*Case ID:* No Case ID

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/fef94c79-e7b2-43b3-8357-b7623a17311an%40googlegroups.com.

Didn't get response for apply for basic access - developer token

2024-04-24 Thread Fernando Silva Vera

I have been waiting for months to be approved for access at the basic 
level, can you help me?

I'm developing an app and I need to have access to test with production 
data, please help, I've been stuck with this for months and I can't get an 
answer

Here is the information:
*Google Ads Manager Account ID (MCC):* 904-417-4760
*Access level:* Basic access requested
*Case ID:* No Case ID

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/e2a60d52-c472-41a1-bbcc-9b4efffe9203n%40googlegroups.com.

[krita] [Bug 484715] crash upon opening past files

2024-03-31 Thread Vera Tymchenko

https://bugs.kde.org/show_bug.cgi?id=484715

--- Comment #4 from Vera Tymchenko  ---
if you look at console lines, it looks like snap package has just used the
wrong (previous) libraries
so all that is needed is to inform the proper package manager

but if I understood you correctly, it's not the KDE or Krita team, that builds
snap images

problem is that Snapcraft points https://snapcraft.io/krita me to Krita's 'get
involved' page 
https://krita.org/en/get-involved/ which literally goes here :)

can you help me to find where to (re)file the bug/issue again so they can build
it normally or fix it?

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 484715] crash upon opening past files

2024-03-30 Thread Vera Tymchenko

https://bugs.kde.org/show_bug.cgi?id=484715

Vera Tymchenko  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #2 from Vera Tymchenko  ---
I'm not sure installing AppImage on this machine is a good idea.

Nevertheless, I have uninstalled snap to try the APT version at least, only to
learn there are only VERY outdated apt versions in backports like 5.0.2. I have
installed snap again and now it starts and immediately crashes after I see
briefly splash picture. 

If I start it from the command line, the console output looks like this:
$ krita
Qt: Session management error: Could not open network socket
libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs
'23.2.1-1ubuntu3.1~22.04.2')
libGL error: failed to load driver: iris
libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs
'23.2.1-1ubuntu3.1~22.04.2')
libGL error: failed to load driver: iris
libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs
'23.2.1-1ubuntu3.1~22.04.2')
libGL error: failed to load driver: swrast
libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs
'23.2.1-1ubuntu3.1~22.04.2')
libGL error: failed to load driver: iris
libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs
'23.2.1-1ubuntu3.1~22.04.2')
libGL error: failed to load driver: iris
libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs
'23.2.1-1ubuntu3.1~22.04.2')
libGL error: failed to load driver: swrast
Qt: Session management error: Could not open network socket
Invalid profile :  "/snap/krita/100/usr/share/color/icc/colord/Crayons.icc"
Invalid profile :  "/snap/krita/100/usr/share/color/icc/colord/x11-colors.icc"
Cannot mix incompatible Qt library (5.15.11) with this library (5.15.12)
Aborted (core dumped)

It says there is coredump but it's certainly not in the usual place of
/var/crash so I can't provide it.
And /snap sub-tree doesn't have it either
$ ll /snap/krita/current/var/
total 0
drwxr-xr-x  3 root root  26 maalis 29 10:49 ./
drwxr-xr-x 13 root root 195 maalis 29 10:49 ../
drwxr-xr-x  3 root root  27 maalis 29 10:49 lib/

I would like to avoid AppImage as in the past they were poorly behaving on this
system.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 484715] New: crash upon opening past files

2024-03-29 Thread Vera Tymchenko

https://bugs.kde.org/show_bug.cgi?id=484715

Bug ID: 484715
   Summary: crash upon opening past files
Classification: Applications
   Product: krita
   Version: 5.2.2
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: * Unknown
  Assignee: krita-bugs-n...@kde.org
  Reporter: vera.tymche...@gmail.com
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY


STEPS TO REPRODUCE
1. open krita
2. select past file from Open file dialog
3. click to open

OBSERVED RESULT
krita crashes on some files and doesn't crash on others, in particular image
projects seem to open fine, animated ones crash

EXPECTED RESULT
any random opened past file opens no problem

SOFTWARE/OS VERSIONS
Ubuntu Mate 24.04.4 LTS Jammy
main desktop is mate
Krita is from snap 

ADDITIONAL INFORMATION
$ snap info krita
name:  krita
summary:   Digital Painting, Creative Freedom
publisher: Stichting Krita Foundation (krita✓)
store-url: https://snapcraft.io/krita
contact:   https://krita.org/en/get-involved/overview/
license:   unset
description: |
  Krita is the full-featured digital art studio.

  It is perfect for sketching and painting, and presents an end–to–end solution
for creating digital
  painting files from scratch by masters.

  Krita is a great choice for creating concept art, comics, textures for
rendering and matte
  paintings. Krita supports many colorspaces like RGB and CMYK  at 8 and 16
bits integer channels,
  as well as 16 and 32 bits floating point channels.

  Have fun painting with the advanced brush engines, amazing filters and many
handy features that
  make Krita enormously productive.
commands:
  - krita
snap-id:  r8Shy9i0XE50a3tUlChg3tvjSeLGJ4Za
tracking: latest/stable
refresh-date: today at 16:55 EET
channels:
  latest/stable:5.2.2 2024-03-29 (100) 504MB -
  latest/candidate: 5.2.2 2024-03-29 (100) 504MB -
  latest/beta:  ↑
  latest/edge:  ↑
installed:  5.2.2(100) 504MB -

-- 
You are receiving this mail because:
You are watching all bug changes.

[Corpora-List] SIGDIAL 2024: Call for Papers

2024-02-25 Thread Vera Demberg via Corpora

re available as an Overleaf template
<https://www.overleaf.com/read/crtcwgxzjskr>and also downloadable
directly <https://github.com/acl-org/acl-style-files>(Latex and Word)


Submissions must conform to the official ACL style guidelines, which are
contained in these templates. Submissions must be electronic, in PDF format.


Submission Deadline


SIGDIAL will accept regular submissions through the Softconf/START
system, as well as commitment of already reviewed papers through the ACL
Rolling Review (ARR) system.


Regular submission


Authors have to fill in the submission form in the Softconf/START system
and upload an initial pdf of their papers before May 17, 2024(23:59
GMT-11).  Details and the submission link will be posted on the
conference website <https://2024.sigdial.org/>.


Submissionvia ACL Rolling Review (ARR) <https://aclrollingreview.org/>


Please refer to the ARR Call for Papers
<https://aclrollingreview.org/cfp>for detailed information about
submission guidelines to ARR. The commitment deadline for authors to
submit their reviewed papers, reviews, and meta-review to SIGDIAL 2024
is June 19, 2024. Note that the paper needs to be fully reviewed by ARR
in order to make a commitment, thus the latest date for ARR submission
will be April 15, 2024.


Mentoring


Acceptable submissions that require language (English) or organizational
assistance will be flagged for mentoring, and accepted with a
recommendation to revise with the help of a mentor. An experienced
mentor who has previously published in the SIGDIAL venue will then help
the authors of these flagged papers prepare their submissions for
publication.


Best Paper Awards


In order to recognize significant advancements in dialogue/discourse
science and technology, SIGDIAL 2024 will include best paper awards. All
papers at the conference are eligible for the best paper awards. A
selection committee consisting of prominent researchers in the fields of
interest will select the recipients of the awards.




SIGDIAL 2024 Program Committee

Vera Demberg and Stefan Ultes

Conference Website: https://2024.sigdial.org/ <https://2024.sigdial.org/>



*
___
Corpora mailing list -- corpora@list.elra.info
https://list.elra.info/mailman3/postorius/lists/corpora.list.elra.info/
To unsubscribe send an email to corpora-le...@list.elra.info

Re: [Vote] Bump the Lucene main branch to Java 21

2024-02-23 Thread Ignacio Vera

+1

On Fri, Feb 23, 2024 at 3:34 PM Benjamin Trent 
wrote:

> +1
>
> On Fri, Feb 23, 2024 at 8:54 AM Adrien Grand  wrote:
>
>> +1
>>
>> On Fri, Feb 23, 2024 at 12:54 PM Uwe Schindler  wrote:
>> >
>> > Here is my +1
>> >
>> > Uwe
>> >
>> > Am 23.02.2024 um 12:24 schrieb Chris Hegarty:
>> > > Hi,
>> > >
>> > > Since the discussion on bumping the Lucene main branch to Java 21 is
>> winding down, let's hold a vote on this important change.
>> > >
>> > > Once bumped, the next major release of Lucene (whenever that will be)
>> will require a version of Java greater than or equal to Java 21.
>> > >
>> > > The vote will be open for at least 72 hours (and allow some
>> additional time for the weekend) i.e. until 2024-02-28 12:00 UTC.
>> > >
>> > > [ ] +1  approve
>> > > [ ] +0  no opinion
>> > > [ ] -1  disapprove (and reason why)
>> > >
>> > > Here is my +1
>> > >
>> > > -Chris.
>> > > -
>> > > 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
>> >
>>
>>
>> --
>> Adrien
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>>

Re: [VOTE] Release Lucene 9.9.2 RC1

2024-01-25 Thread Ignacio Vera

+1

SUCCESS! [0:54:32.772088]

On Thu, Jan 25, 2024 at 11:23 PM Uwe Schindler  wrote:

> Hi,
>
> +1 to release.
>
> Tested smoketester with Java 11 and 17; results:
> https://jenkins.thetaphi.de/job/Lucene-Release-Tester/31/console
>
> Uwe
>
> Am 25.01.2024 um 12:57 schrieb Chris Hegarty:
> > Please vote for release candidate 1 for Lucene 9.9.2
> >
> > The artifacts can be downloaded from:
> >
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.2-RC1-rev-a2939784c4ca60bc28bf488b5479c02fc2e5e22c
> >
> > You can run the smoke tester directly with this command:
> >
> > python3 -u dev-tools/scripts/smokeTestRelease.py \
> >
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.2-RC1-rev-a2939784c4ca60bc28bf488b5479c02fc2e5e22c
> >
> > The vote will be open for 96 hours ( allowing some additional time for
> weekend span) i.e. until 2024-01-29 12:00 UTC.
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Here is my +1
> >
> > Draft release notes can be found at
> https://cwiki.apache.org/confluence/display/LUCENE/ReleaseNote9_9_2
> >
> > -Chris.
> >
> >
> > -
> > 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
>
>

[dspace-tech] Re: mvn package failed for DSpace Cris 2023.01.00 on Debian 12

2024-01-04 Thread Rodrigo Vera

hello, I'm having the same trouble but with latest version 2023.02.01.

How did you fix this ? if you fixed it.

thanks in advance

rodrigo

On Thursday, August 17, 2023 at 10:05:57 AM UTC-4 Armin Wenz wrote:

> Hi all,
>
> I have a fresh installed Debian 12 machine, maven 3.8.7, openjdk version 
> "17.0.8"
>
> I follwed the DSpace installation process described in 
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace
>
> I checked out DSpace Cris dspace-cris-2023.01.00. Haven't done any 
> modifications except in local.cfg
>
> When running 'mvn package' it fails with the error
>
> Failed to execute goal on project additions: Could not resolve 
> dependencies for project 
> org.dspace.modules:additions:jar:cris-2023.01.01-SNAPSHOT: The following 
> artifacts could not be resolved: 
> org.dspace:dspace-api:jar:cris-2023.01.01-SNAPSHOT, 
> org.dspace:dspace-api:jar:tests:cris-2023.01.01-SNAPSHOT, 
> org.dspace:dspace-services:jar:cris-2023.01.01-SNAPSHOT: Could not find 
> artifact org.dspace:dspace-api:jar:cris-2023.01.01-SNAPSHOT in 
> maven-central (https://repo.maven.apache.org/maven2)
>
> The only unusual stuff I find in the logs (mvn -e) is
>
> [WARNING] The POM for org.dspace:dspace-api:jar:cris-2023.01.00 is 
> missing, no dependency information available
> [WARNING] The POM for org.dspace:dspace-api:jar:tests:cris-2023.01.00 is 
> missing, no dependency information available
> [WARNING] The POM for org.dspace:dspace-services:jar:cris-2023.01.00 is 
> missing, no dependency information available
>
> when building DSpace Kernel :: Additions and Local Customizations 
> cris-2023.01.00 [2/4]
>
> Just for testing purposes I did 'mvn package' on the same machine with 
> DSpace 7.6, which compiles fine.
>
> Due to the above error I also checked the existence of the POM files in 
> DSpace 7.6 and DSpace Cris. I found the same files (by name).
>
> Does anybody have a glue what I may have missed or what could be wrong.
>
> I've attached the mvn logs (done with 'mvn --color never -X package'). 
> Maybe anybody recognize the error.
>
> Thanks
>
> -- 
> Armin Wenz
> Universitätsbibliothek Mainz
> Leitung Bibliotheksanwendungen
> Jakob-Welder-Weg 12
> 55128 Mainz
> Tel.: +49 6131 39-29830 <+49%206131%203929830>
> http://www.ub.uni-mainz.de

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/45813735-4eb2-4ef8-aa12-f4c128f03c0bn%40googlegroups.com.

[Corpora-List] NLP positions / CS @ Max Planck PhD Program - Call for Applicants

2023-12-19 Thread Vera Demberg via Corpora


Please note that students in NLP are also very welcome to apply to the
CS @ Max Planck PhD Program; NLP Faculty in this program include e.g.
Mariya Toneva and Vera Demberg.

CS @ Max Planck is a selective doctoral program that grants
admitted students full financial support to pursue doctoral research
in the field of computer and information science, with faculty at Max
Planck Institutes and some of the best German universities.

To qualify for the program, students must hold a Bachelor’s or
Master’s degree in computer science (or a related field) and have an
outstanding academic record.  We especially encourage applications
from students who wish to explore research across the CS spectrum
before committing to a topic and advisor.

For more information about the program, see:
https://www.cis.mpg.de/graduate-programs/cs-max-planck

The next application deadline is December 31, 2023.


For further information, please contact Gretchen Gravelle (MPI-SWS Grad
Office, grad-off...@mpi-sws.org)

___
Corpora mailing list -- corpora@list.elra.info
https://list.elra.info/mailman3/postorius/lists/corpora.list.elra.info/
To unsubscribe send an email to corpora-le...@list.elra.info

[Corpora-List] 6 PhD students and 1 Postdoc: Neuroexplicit Models of Language, Vision, and Action - Saarbrücken, Germany

2023-12-17 Thread Vera Demberg via Corpora


**

*The Research Training Group 2853 “Neuroexplicit Models of Language,
Vision, and Action” is looking for*

*

6 PhD students - September 2024

1 Postdoc - March 2024 or later


Neuroexplicit models combine neural and human-interpretable (“explicit”)
models in order to overcome the limitations that each model class has
separately. They include neurosymbolic models, which combine neural and
symbolic models, but also e.g. combinations of neural and physics-based
models. In the RTG, we will improve the state of the art in natural
language processing (“Language”), computer vision (“Vision”), and
planning and reinforcement learning (“Action”) through the use of
neuroexplicit models and investigate the cross-cutting design principles
of effective neuroexplicit models (“Foundations”).


The RTG is scheduled to grow to a total of 24 PhD students and one
postdocby 2025; the first six PhD students started in late 2023. Through
the inclusion of ~20 further PhD students and postdocs funded from other
sources, it will be one of the largest research centers on neuroexplicit
or neurosymbolic models in the world. The RTG brings together
researchers at Saarland University, the Max Planck Institute for
Informatics, the Max Planck Institute for Software Systems, the CISPA
Helmholtz Center for Information Security, and the German Research
Center for Artificial Intelligence (DFKI). All of these institutions are
colocated on the same campus in Saarbrücken, Germany.


The positions are funded as follows:


 *

   PhD students will be funded for up to four years at the TV-L E13
   100% pay scale. You should have or be about to complete an MSc
   degree in computer science or a related field and have demonstrated
   expertise in one of the research areas of the RTG, e.g. through an
   excellent Master’s thesis or relevant publications.

 *

   The postdoc will initially be funded for three years, with the
   possibility of extension up to five years, at the TV-L E13 100% pay
   scale.As the RTG postdoc, you will pursue your own research agenda
   in the field of neuroexplicit models and work with the PhD students
   to identify and pursue opportunities for collaborative research. You
   should have or be about to complete a PhD in computer science or a
   related field and have demonstrated your expertise in one or more of
   the RTG’s research areas through publications in top venues.


The RTG is part of the Saarland Informatics Campus, one of the leading
centers for researchin computer science, artificial intelligence, and
natural language processing in Europe. The Saarland Informatics Campus
brings together 900 researchers and 2500 students from 81 countries. The
CISPA Helmholtz Center, located on the same campus, is home to an
additional 350 researchers and on track to grow to 800 by 2026.
Researchers at SIC and CISPA are part of the ELLIS network and have been
awarded more than 35 ERC grants.


Each PhD student in the RTG will be jointly supervised by two PhD
advisorsfrom the list of Principal Investigators below. Each student
will freely define their own research topic; we encourage the choice of
topics that cross the traditional boundaries of research fields.
Students may be affiliated with Saarland University or with one of the
participating institutes.


Vera Demberg, Saarland University - Computational Linguistics

Jörg Hoffmann, Saarland University - AI Planning

Eddy Ilg, Saarland University - Computer Vision, Machine Learning

Dietrich Klakow, Saarland University - Natural Language Processing

Alexander Koller, Saarland University - Computational Linguistics

Bernt Schiele, MPI for Informatics - Computer Vision, Machine Learning

Philipp Slusallek, DFKI and Saarland University - Computer Graphics,
Artificial Intelligence

Christian Theobalt, MPI for Informatics - Visual Computing, Machine Learning

Mariya Toneva, MPI for Software Systems - Computational Neuroscience,
Machine Learning

Isabel Valera, Saarland University - Machine Learning

Jilles Vreeken, CISPA - Machine Learning, Causality

Joachim Weickert, Saarland University - Mathematical Data Analysis

Verena Wolf, DFKI and Saarland University - Modeling and Simulation,
Reinforcement Learning


Ellie Pavlick, Brown University and Google AI, will join us regularly as
a Mercator Fellow.


Please send your application by 7 January 2024to ap...@neuroexplicit.org
<mailto:ap...@neuroexplicit.org>. Include the reference number W2298 for
the postdoc position and the reference number W2299 for the PhD
positions. We aim to conduct job interviews in July (for a start in
October) and September (for a later start). The legally binding version
of this job ad is at

https://www.uni-saarland.de/fileadmin/upload/verwaltung/stellen/Wissenschaftler/W2412.pdf
<https://www.uni-saarland.de/fileadmin/upload/verwaltung/stellen/Wissenschaftler/W2412.pdf>

(postdoc) and

https://www.uni-saarland.de/fileadmin/upload/verwaltung/stellen/Wissenschaftler/W2411.pdf
<

[dspace-tech] Re: Unsatisfied dependency on startup

2023-12-04 Thread Rodrigo Vera

Hello, 

ran into the same problem, fixed by runnning

mvn clean install 

before mvn package (maybe not necessary after all). also make sure you're 
running same java version in mvn, ant and tomcat. 

greetings.

On Friday, December 1, 2023 at 3:28:10 PM UTC-3 Steve Michaels wrote:

> Now that I've got the database migrated, startup is giving me an 
> unsatisfied dependency error: 
>
> 01-Dec-2023 13:00:22.633 SEVERE [http-nio-8080-exec-7] 
> org.apache.catalina.core.ApplicationContext.log HTMLManager: Error starting 
> [/server]
> org.apache.catalina.LifecycleException: Failed to start component 
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/server]]
> at 
> org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)
> at 
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198)
> at 
> org.apache.catalina.manager.ManagerServlet.start(ManagerServlet.java:1437)
> at 
> org.apache.catalina.manager.HTMLManagerServlet.start(HTMLManagerServlet.java:703)
> at 
> org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:221)
> at 
> javax.servlet.http.HttpServlet.service(HttpServlet.java:681)
> at 
> javax.servlet.http.HttpServlet.service(HttpServlet.java:764)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:227)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
> at 
> org.apache.catalina.filters.CsrfPreventionFilter.doFilter(CsrfPreventionFilter.java:211)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
> at 
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
> at 
> org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:126)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:197)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)
> at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:659)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:135)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
> at 
> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:687)
> at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78)
> at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:359)
> at 
> org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:399)
> at 
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
> at 
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:889)
> at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1735)
> at 
> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
> at 
> org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
> at 
> org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
> at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: 
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
> creating bean with name 'authenticationRestController': Unsatisfied 
> dependency expressed through field 'converter'; nested exception is 
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
> creating bean with name 'converterService': Unsatisfied dependency 
> expressed through field 'converters'; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating 
> bean with name 'workflowItemConverter'

Re: [VOTE] Release Lucene 9.9.0 RC2

2023-12-01 Thread Ignacio Vera

SUCCESS! [1:20:23.570231]


+1

On Fri, Dec 1, 2023 at 6:55 AM Shyamsunder Mutcha  wrote:

> SUCCESS! [0:38:41.054860]
> +1
>
> On Thu, Nov 30, 2023 at 9:59 PM Nhat Nguyen 
> wrote:
>
>> SUCCESS! [1:22:43.808415]
>>
>> +1
>>
>> On Thu, Nov 30, 2023 at 6:09 PM Christian Moen  wrote:
>>
>>> SUCCESS! [1:49:26.873909]
>>>
>>> +1
>>>
>>> On Fri, Dec 1, 2023 at 3:09 AM Chris Hegarty
>>>  wrote:
>>>
 Please vote for release candidate 2 for Lucene 9.9.0


 The artifacts can be downloaded from:


 https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC2-rev-06070c0dceba07f0d33104192d9ac98ca16fc500


 You can run the smoke tester directly with this command:


 python3 -u dev-tools/scripts/smokeTestRelease.py \


 https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC2-rev-06070c0dceba07f0d33104192d9ac98ca16fc500


 The vote will be open for at least 72 hours, and given the weekend in
 between, let’s keep it open until 2023-12-04 12:00 UTC.

 [ ] +1  approve

 [ ] +0  no opinion

 [ ] -1  disapprove (and reason why)


 Here is my +1


 -Chris.

Re: [VOTE] Release Lucene 9.9.0 RC1

2023-11-30 Thread Ignacio Vera

SUCCESS! [0:52:59.891964]


+1

On Thu, Nov 30, 2023 at 12:42 PM Michael McCandless <
luc...@mikemccandless.com> wrote:

> +1 to release.
>
> I hit a corner-case test failure and opened a PR to fix it:
> https://github.com/apache/lucene/pull/12859
>
> I don't think this should block the release? -- it looks exotic.
>
> Thanks Chris!
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Thu, Nov 30, 2023 at 1:16 AM Patrick Zhai  wrote:
>
>> SUCCESS! [1:03:54.880200]
>>
>> +1. Thank you Chris!
>>
>> On Wed, Nov 29, 2023 at 8:45 PM Nhat Nguyen
>>  wrote:
>>
>>> SUCCESS! [1:11:30.037919]
>>>
>>> +1. Thanks, Chris!
>>>
>>> On Wed, Nov 29, 2023 at 8:53 AM Chris Hegarty
>>>  wrote:
>>>
 Hi,


 Please vote for release candidate 1 for Lucene 9.9.0


 The artifacts can be downloaded from:


 https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC1-rev-92a5e5b02e0e083126c4122f2b7a02426c21a037


 You can run the smoke tester directly with this command:


 python3 -u dev-tools/scripts/smokeTestRelease.py \


 https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC1-rev-92a5e5b02e0e083126c4122f2b7a02426c21a037


 The vote will be open for at least 72 hours, and given the weekend in
 between, let’s it open until 2023-12-04 12:00 UTC.


 [ ] +1  approve

 [ ] +0  no opinion

 [ ] -1  disapprove (and reason why)


 Here is my +1


 Draft release highlights can be viewed here (comments and feedback
 welcome):
 https://cwiki.apache.org/confluence/display/LUCENE/ReleaseNote9_9_0

 -Chris.

>>>

[Corpora-List] Postdoc in cognitive modelling of language processing at Saarland University

2023-11-17 Thread Vera Demberg via Corpora


2-year postdoctoral position

We are inviting applications for one postdoctoral position (funding
available until 01/2026, start date flexible; contract renewal may be
possible afterwards) of a computer scientist, cognitive scientist,
computational linguist or psycholinguist, who has experience with or
interest in experimental research and/or cognitive modelling for
language processing (e.g., Bayesian models, and/or models using
cognitive architectures like ACT-R; the use of LLMs and their
combination with cognitive architectures will also be explored).

The position will be funded as part of the ERC Starting Grant
"Individualized Interaction in Discourse" of Prof. Vera Demberg, at
Saarland University. The goal of the position is to develop models that
capture individual differences in discourse and pragmatic processing.

The candidate will conduct research on the design and implementation of
psycholinguistic experiments and/or cognitive models of language
processing at the level of discourse and/or pragmatic processing. These
models should capture individual differences in cognition such as
working memory, language experience, background knowledge,
theory-of-mind abilities etc.
The successful applicant must have excellent spoken and written
proficiency in English, and have a background in natural language
processing or cognitive modelling.

This is a position on the German TV-L E13 scale (100% position at the
postdoc level). The starting salary of a 100% TV-L E13 position is a bit
over 50,000 Euros per year and increases with experience. The initial
appointment will be for three years; the position can be extended up to
the limits of the German law for academic contracts (WissZeitVG). The
starting date is January 2024 or later; we would be willing to adapt to
the time requirements of an ideal candidate.


About the research environment

Saarland University is one of the leading centers for computational
linguistics and computer science in Europe, and offers a dynamic and
stimulating research environment. The Department of Language Science and
Technology consists of about 100 research staff in nine research groups
in the fields of computational linguistics, psycholinguistics, speech
processing, and corpus linguistics. Saarland University is one of the
leading centres for computer science and computational linguistics in
Europe, and offers a dynamic and stimulating research environment. The
group is affiliated with both the Department of Computer Science, with
the Department of Language Science and Technology and with the MPI for
Informatics.


The department is a core member of the new Research Training Group
"Neuroexplicit Models of Language, Vision, and Action", which is on
track to grow into one of the largest centers for research on
neurosymbolic models in NLP and other fields of AI in the world. It is
also the centerpiece of the Collaborative Research Center 1102
"Information Density and Linguistic Encoding" and part of the Saarland
Informatics Campus, which brings together computer science research at
the university with world-class research institutions on campus, such as
the Max Planck Institute for Informatics, the Max Planck Institute for
Software Systems, and the German Research Center for Artificial
Intelligence (DFKI). The Saarland Informatics Campus brings together 900
researchers and 2100 students from 81 countries; SIC faculty have won 36
ERC grants.

Saarland University is located in Saarbrücken, a mid-sized city in the
tri-border area of Germany, France, and Luxembourg. Saarbrücken combines
a lively culture scene with a relaxed atmosphere, and is quite an
affordable place to live in. Our department maintains an international
and diverse work environment. The primary working language is English;
learning German while you are here will make it easier to connect with
the local culture, but is not necessary for your work.


How to apply

Please submit your application by email to
applications...@lst.uni-saarland.de. Preference will be given to
applications received by
*6 December 2023*.

Please quote opening number W2403 in your application materials.

Include a single PDF file with the following information:
• a statement of research interests that motivates why you are applying
for this position and outlines your research agenda;
• a full CV including your list of publications;
• scans of transcripts and academic degree certificates;
• the names, affiliations, and e-mail addresses of two people who can
provide letters of reference for you.

Saarland University especially welcomes applications from women and
people with disabilities.

If you have further questions, please email Vera Demberg
.
___
Corpora mailing list -- corpora@list.elra.info
https://list.elra.info/mailman3/postorius/lists/corpora.list.elra.info/
To unsubscribe send an email to corpora-le...@list.elra.info

[Corpora-List] Postdoc in NLP or psycholinguistics at Saarland University

2023-11-17 Thread Vera Demberg via Corpora


Research and teaching position at Saarland University, Saarbrücken, Germany

Start date: early 2024
Contract duration: 3 years (can be extended)
Payscale: E13 100% (postdoc)

We are looking to fill a research and teaching position in NLP or
psycholinguistics at the at the research group of Prof. Vera Demberg. It
offers great flexibility in developing your own research and teaching
agenda, and collaborations with other research groups within the
department of Language Science and Technology and/or at the department
of Computer Science are encouraged.

The position is flexible with respect to topic, but it should connect
thematically with current topics of interest to the research group.
These include neural natural language generation with specific focus on
data-to-text generation, avoidance of hallucinations and personalized
language generation, as well as computational models of discourse
processing and pragmatics. Psycholinguistic experimental work within our
group revolves around information-theoretic accounts of human language
processing, as well as discourse processing and experimental pragmatics.
We are especially interested in individual differences in discourse and
pragmatic processing (see also our ERC project "Individualized
Interaction in Discourse"). You should have expertise in neural and/or
linguistically principled methods in NLP, or experimental methods for
psycholinguistics.

The position includes a teaching load of up to four hours per week and
can be given within the BSc or MSc programs in Computational
Linguistics, Computer Science or Data Science and Artificial
Intelligence. Our study programs attract excellent and highly motivated
students; it is not unusual for our students to publish papers at
peer-reviewed conferences before graduation. The MSc students in
particular are a very international crowd, with two thirds joining us
from abroad. You will typically teach one seminar per semester on a
topic of your choice, which will allow you to motivate students to do
BSc and MSc theses under your supervision.

This is a position on the German TV-L E13 scale (100% position at the
postdoc level). The starting salary of a 100% TV-L E13 position is a bit
over 50,000 Euros per year and increases with experience. The initial
appointment will be for three years; the position can be extended up to
the limits of the German law for academic contracts (WissZeitVG). The
starting date is January 2024 or later; we would be willing to adapt to
the time requirements of an ideal candidate.


Requirements

We are looking for candidates who have finished, or are about to
complete, an excellent PhD degree in computational linguistics, computer
science, psycholinguistics or a related discipline. You must be
proficient in English (spoken and written). Applicants should have
demonstrated their research expertise through high-quality publications.


About the research environment

Saarland University is one of the leading centers for computational
linguistics and computer science in Europe, and offers a dynamic and
stimulating research environment. The Department of Language Science and
Technology consists of about 100 research staff in nine research groups
in the fields of computational linguistics, psycholinguistics, speech
processing, and corpus linguistics.

The department is a core member of the new Research Training Group
"Neuroexplicit Models of Language, Vision, and Action", which is on
track to grow into one of the largest centers for research on
neurosymbolic models in NLP and other fields of AI in the world. It is
also the centerpiece of the Collaborative Research Center 1102
"Information Density and Linguistic Encoding" and part of the Saarland
Informatics Campus, which brings together computer science research at
the university with world-class research institutions on campus, such as
the Max Planck Institute for Informatics, the Max Planck Institute for
Software Systems, and the German Research Center for Artificial
Intelligence (DFKI). The Saarland Informatics Campus brings together 900
researchers and 2100 students from 81 countries; SIC faculty have won 36
ERC grants.

Saarland University is located in Saarbrücken, a mid-sized city in the
tri-border area of Germany, France, and Luxembourg. Saarbrücken combines
a lively culture scene with a relaxed atmosphere, and is quite an
affordable place to live in. Our department maintains an international
and diverse work environment. The primary working language is English;
learning German while you are here will make it easier to connect with
the local culture, but is not necessary for your work.


How to apply:

Please submit your application by email to
applications...@lst.uni-saarland.de. Preference will be given to
applications received by 6 December 2023. Please cite opening number
2402 when sending in your application materials.

Include a single PDF file with the following information:
• a statement of research in

Re: Welcome Patrick Zhai to the Lucene PMC

2023-11-11 Thread Ignacio Vera

Welcome Patrick!

On Sat, Nov 11, 2023 at 3:29 PM Uwe Schindler  wrote:

> Welcome Patrick!
>
> Uwe
>
>
> Am 10. November 2023 21:04:32 MEZ schrieb Michael McCandless <
> luc...@mikemccandless.com>:
>
>> I'm happy to announce that Patrick Zhai has accepted an invitation to
>> join the Lucene Project Management Committee (PMC)!
>>
>> Congratulations Patrick, thank you for all your hard work improving
>> Lucene's community and source code, and welcome aboard!
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
> --
> Uwe Schindler
> Achterdiek 19, 28357 Bremen
> https://www.thetaphi.de
>

[Corpora-List] reminder: PhD position in Cognitive Modelling

2023-06-15 Thread Vera Demberg via Corpora


We are inviting applications for one PhD position (3 years) of acomputer
scientist,computational linguistor psycholinguist,who has experience
withor interest incognitive modelling for language processing (e.g.,
Bayesian models, and/or modelsusing cognitive architectureslike ACT-R).

Theposition will be funded as part of theERC Starting Grant
"Individualized Interaction in Discourse" ofProf. Vera Demberg, at
Saarland University. The goal of the position is todevelop models that
capture individualdifferences in discourse and pragmatic processing.

The candidatewill conduct research on the design andimplementation of
cognitive models of language processingat the level of discourse and/or
pragmatic processing. These models should capture individual differences
in cognitionsuch as working memory, language experience, background
knowledge, theory-of-mind abilities etc.
The successful applicant must have excellent spoken and
writtenproficiency inEnglish, and have a background in natural language
processing or cognitive modelling.

Applicants are requested to submit their application, including a cover
letter that specifies why you would like to workon this topic and what
qualifies you for it, an academic CV, a list of academic publications,
yourBSc/ MSc thesis (ora current draft), copies of academic degree
certificates and names of two potential references.

For application to the PhD position please quote opening number W2289.

The applicationsshould be sent via emaildirectly to Prof. Vera Demberg:
vera(at)coli.uni-saarland.de


*Theapplication deadline isJune 18th**, 202**3*

Saarland University is one of the leading centres for computer science
and computational linguistics in Europe, and offers adynamic and
stimulating research environment.The groupis affiliated with both
theDepartment of Computer Scienceand withtheDepartment of Language
Scienceand Technology.
Both departments are part of the Saarland Informatics Campus, which
brings together 800 researchers and 2000 students from 81countries. We
collaborate closely with the university's Department of Computer
Science, the Max Planck Institute for Informatics,the Max Planck
Institute for Software Systems, and the German Research Center for
Artificial Intelligence (DFKI).
Our researchers and students come from all over the world, and our
primary working language is English.
The Saarland University is an equal opportunities employer. In
accordance with its policy of increasing the proportion of womenin this
type of employment, the University actively encourages applications from
women. Women are given preference in cases ofequal suitability, ability
and professional performance.
Applications from severely disabled persons will be given preferential
consideration in the event of equal suitability. Part-timeemployment is
generally possible.
We welcome applications regardless of gender,nationality, ethnic and
social origin, religion/belief, disability, age, and sexualorientation
and identity.

Pay grade classification is based on the particular details of the
position held and the extent to which the applicant meetstherequirements
of the pay grade within the TV-L salary scale.
Unfortunately, costs for attending an interview at Saarland University
cannot be reimbursed in principle.
When you submit a job application to Saarland University you will be
transmitting personal data.Please refer to our privacy noticefor
information on how we collect and process personal data in accordance
with Art.13 of theDatenschutz-Grundverordnung.Bysubmitting your
application you confirm that you have taken note of the information in
the Saarland University privacy notice.

--
Prof. Dr. Vera Demberg
Computer Science and Computational Linguistics
Saarland Informatics Campus
Saarland University
Campus C7.2 Room 3.02
D-66123 Saarbrücken
Phone: +49-681-302-70024
Sekretariat: +49-681-302-70025
Fax: +49-681-302-70026
___
Corpora mailing list -- corpora@list.elra.info
https://list.elra.info/mailman3/postorius/lists/corpora.list.elra.info/
To unsubscribe send an email to corpora-le...@list.elra.info

Re: Lucene 9.7 release

2023-06-09 Thread Ignacio Vera

+1

On Fri, Jun 9, 2023 at 6:20 PM Tomás Fernández Löbbe 
wrote:

> +1
> Thanks Adrien
>
> On Fri, Jun 9, 2023 at 9:19 AM Michael McCandless <
> luc...@mikemccandless.com> wrote:
>
>> +1, thanks Adrien!
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>>
>> On Fri, Jun 9, 2023 at 12:11 PM Patrick Zhai  wrote:
>>
>>> +1, thank you Adrien!
>>>
>>> On Fri, Jun 9, 2023, 09:08 Adrien Grand  wrote:
>>>
 Hello all,

 There is some good stuff that is scheduled for 9.7 already, I found the
 following changes in the changelog that look especially interesting:
  - Concurrent query rewrites for vector queries.
  - Speedups to vector indexing/search via integration of the Panama
 vector API.
  - Reduced overhead of soft deletes.
  - Support for update by query.

 I propose we start the process for a 9.7 release, and I volunteer to be
 the release manager. I suggest the following schedule:
  - Feature freeze on June 16th, one week from now. This is when the 9.7
 branch will be cut.
  - Open a vote on June 21st, which we'll possibly delay if blockers get
 identified.

 --
 Adrien

>>>

[Corpora-List] extended deadline: PhD and Postdoc position in Cognitive Modelling

2023-05-22 Thread Vera Demberg via Corpora

We are inviting applications for one PhD position (3 years) and a
postdoctoral position (funding available 09/2023-01/2026)of acomputer
scientist,computational linguistor psycholinguist,who has experience
withor interest incognitive modelling for language processing (e.g.,
Bayesian models, and/or modelsusing cognitive architectureslike ACT-R).

Thepositions will be funded as part of theERC Starting Grant
"Individualized Interaction in Discourse" ofProf. Vera Demberg, at
Saarland University. The goal of the position is todevelop models that
capture individualdifferences in discourse and pragmatic processing.

The candidatewill conduct research on the design andimplementation of
cognitive models of language processingat the level of discourse and/or
pragmatic processing. These models should capture individual differences
in cognitionsuch as working memory, language experience, background
knowledge, theory-of-mind abilities etc.
The successful applicant must have excellent spoken and
writtenproficiency inEnglish, and have a background in natural language
processing or cognitive modelling.

Applicants are requested to submit their application, including a cover
letter that specifies why you would like to workon this topic and what
qualifies you for it, an academic CV, a list of academic publications,
yourBSc/ MSc / PhDthesis (ora current draft), copies of academic degree
certificates and names of two potential references.

For application to the Postdoctoral position, please quote opening
number W2290, for the PhD position please quote opening number W2289.

The applicationsshould be sent via emaildirectly to Prof. Vera Demberg:
vera(at)coli.uni-saarland.de

*The**(extended) **application deadline is**June**4th, 202**3*

Saarland University is one of the leading centres for computer science
and computational linguistics in Europe, and offers adynamic and
stimulating research environment.The groupis affiliated with both
theDepartment of Computer Scienceand withtheDepartment of Language
Scienceand Technology.
Both departments are part of the Saarland Informatics Campus, which
brings together 800 researchers and 2000 students from 81countries. We
collaborate closely with the university's Department of Computer
Science, the Max Planck Institute for Informatics,the Max Planck
Institute for Software Systems, and the German Research Center for
Artificial Intelligence (DFKI).
Our researchers and students come from all over the world, and our
primary working language is English.
The Saarland University is an equal opportunities employer. In
accordance with its policy of increasing the proportion of womenin this
type of employment, the University actively encourages applications from
women. Women are given preference in cases ofequal suitability, ability
and professional performance.
Applications from severely disabled persons will be given preferential
consideration in the event of equal suitability. Part-timeemployment is
generally possible.
We welcome applications regardless of gender,nationality, ethnic and
social origin, religion/belief, disability, age, and sexualorientation
and identity.

Pay grade classification is based on the particular details of the
position held and the extent to which the applicant meetstherequirements
of the pay grade within the TV-L salary scale.
Unfortunately, costs for attending an interview at Saarland University
cannot be reimbursed in principle.
When you submit a job application to Saarland University you will be
transmitting personal data.Please refer to our privacy noticefor
information on how we collect and process personal data in accordance
with Art.13 of theDatenschutz-Grundverordnung.Bysubmitting your
application you confirm that you have taken note of the information in
the Saarland University privacy notice.

--
Prof. Dr. Vera Demberg
Computer Science and Computational Linguistics
Saarland Informatics Campus
Saarland University
Campus C7.2 Room 3.02
D-66123 Saarbrücken
Phone: +49-681-302-70024
Sekretariat: +49-681-302-70025
Fax: +49-681-302-70026

--
You received this message because you are subscribed to the Google
Groups "XPRAG Wine Gatherings" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to xpragwine+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/xpragwine/f9d60192-0120-d71e-a864-1d1fe9d4b452%40coli.uni-saarland.de
<https://groups.google.com/d/msgid/xpragwine/f9d60192-0120-d71e-a864-1d1fe9d4b452%40coli.uni-saarland.de?utm_medium=email_source=footer>.
For more options, visit https://groups.google.com/d/optout.
___
Corpora mailing list -- corpora@list.elra.info
https://list.elra.info/mailman3/postorius/lists/corpora.list.elra.info/
To unsubscribe send an email to corpora-le...@list.elra.info

[Corpora-List] PhD and Postdoc position in Cognitive Modelling

2023-05-04 Thread Vera Demberg via Corpora

For application to the Postdoctoral position, please quote opening
number W2290, for the PhD position please quote opening number W2289.

The applicationsshould be sent via emaildirectly to Prof. Vera Demberg:
vera(at)coli.uni-saarland.de

*Theapplication deadline isMay2**1**st**, 202**3*

Re: [VOTE] Release Lucene 9.6.0 RC2

2023-05-03 Thread Ignacio Vera

+1

SUCCESS! [0:42:35.102645]

On Wed, May 3, 2023 at 12:45 PM Alan Woodward  wrote:

> Please vote for release candidate 2 for Lucene 9.6.0
>
> The artifacts can be downloaded from:
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.6.0-RC2-rev-f94cd1750d198cd0294fb1d967c4e511a7035f1e
>
> You can run the smoke tester directly with this command:
>
> python3 -u dev-tools/scripts/smokeTestRelease.py \
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.6.0-RC2-rev-f94cd1750d198cd0294fb1d967c4e511a7035f1e
>
> Given weekends and UK holidays, the vote will be open until next Monday,
> i.e. until 2023-05-08 11:00 UTC.
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Here is my +1
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: [VOTE] Release Lucene 9.6.0 RC1

2023-05-03 Thread Ignacio Vera

+1

SUCCESS! [2:07:32.970671]

On Wed, May 3, 2023 at 5:08 AM Nhat Nguyen 
wrote:

> +1. Thanks Alan!
>
> SUCCESS! [0:48:46.465752]
>
> On Tue, May 2, 2023 at 11:33 AM Alan Woodward 
> wrote:
>
>> Please vote for release candidate 1 for Lucene 9.6.0
>>
>> The artifacts can be downloaded from:
>>
>> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.6.0-RC1-rev-246ac4bcbe6c0ea7bebcc4f90b2be0536f00d842
>>
>> You can run the smoke tester directly with this command:
>>
>> python3 -u dev-tools/scripts/smokeTestRelease.py \
>>
>> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.6.0-RC1-rev-246ac4bcbe6c0ea7bebcc4f90b2be0536f00d842
>>
>> It is another long holiday weekend here in the UK, so the vote is likely
>> to be held open until at least Monday.
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> Here is my +1
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>>

Re: Lucene 9.6 release

2023-04-19 Thread Ignacio Vera

+1

Thanks Alan!

On Wed, Apr 19, 2023 at 1:27 PM Alan Woodward  wrote:

> Hi all,
>
> It’s been a while since our last release, and we have a number of nice
> improvements and optimisations sitting in the 9x branch.  I propose that we
> start the process for a 9.6 release, and I will volunteer to be the release
> manager.  If there are no objections, I will cut a release branch one week
> today, April 26th.
>
> - Alan
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Bug#865975: docker.io: How to reproduce on Virtual Box / Windows host

2023-03-31 Thread Mickaël Vera

Package: docker.io
Version: 20.10.23+dfsg1-1+b3
Followup-For: Bug #865975
X-Debbugs-Cc: vera.mick...@free.fr

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
 Installation of debian testing in Virtual Box (windows 10 Host) and basic 
use of docker.io
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Creation of a VM in Virtual Box, no customization at all
 Installation of debian testing in this VM, no customization at all
 Installation of docker.io
 Open a terminal and execute command "ping google.fr"
 => ping is OK for hours
 In another terminal execute "docker run -dit -p 8080:80 -v 
"$PWD":/usr/local/apache2/htdocs/ httpd:2.4
 After a few seconds (10 - 40s) the ping command displays "Destination Host 
Unreachable"
 docket stop  resolves the problem and ping command immediatly 
reaches destination
 applying iptables commands mentionned above doesn't solve the problem
 configuring docker like this
 /etc/docker/daemon.json:
 {
"iptables": false
 }
 prevents docker from modifying iptables config but doesn't solve the 
problem

   * What was the outcome of this action?
 Systematically, VM access to internet is broken
   * What outcome did you expect instead?
 Same behaviour as in Debian stable, no network broken access
 This nominal usage of docker works in ubuntu 22.10 installed today for 
this test

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/1 CPU thread; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages docker.io depends on:
ii  adduser3.131
ii  containerd 1.6.18~ds1-1+b2
ii  init-system-helpers1.65.2
ii  iptables   1.8.9-2
ii  libc6  2.36-8
ii  libdevmapper1.02.1 2:1.02.185-2
ii  libsystemd0252.6-1
ii  runc   1.1.4+ds1-1+b3
ii  sysvinit-utils [lsb-base]  3.06-2
ii  tini   0.19.0-1

Versions of packages docker.io recommends:
ii  apparmor 3.0.8-3
ii  ca-certificates  20230311
ii  cgroupfs-mount   1.4
ii  git  1:2.39.2-1.1
ii  needrestart  3.6-3
ii  xz-utils 5.4.1-0.2

Versions of packages docker.io suggests:
pn  aufs-tools 
pn  btrfs-progs
pn  debootstrap
pn  docker-doc 
ii  e2fsprogs  1.46.6-1
pn  rinse  
pn  rootlesskit
pn  xfsprogs   
pn  zfs-fuse | zfsutils-linux  

-- no debconf information

RE: [MORPHMET2] programs for generating cranial endocasts

2023-02-23 Thread Vera Weisbecker

Hi Christy,

I have used endomaker a bit for birds and it has been a revelation, it takes 
seconds to create pretty good endocasts that need a little bit of fixing in 
something like geomagic. If I had to do mammals now on the normal endomaker 
package, I would work out the fastest way of  cropping off all the bone that 
isn’t related to surrounding the brain, then wrap the outside skull/close off 
the foramen magnum, and run endomaker. It would still be way faster than manual 
segmentation.

Cheers,

Vera

From: morphmet2@googlegroups.com  On Behalf Of Paul 
Penkalski
Sent: Friday, 24 February 2023 7:09 AM
To: Christy Hipsley 
Cc: Morphmet 
Subject: Re: [MORPHMET2] programs for generating cranial endocasts

Hi Christy,
Another good option is ITK-SNAP: http://www.itksnap.org/<http://www.itksnap.org>

Although it isn't designed specifically to segment endocraniums, it
has several automatic algorithms that I've used to segment fossil
braincases automatically and it worked really well. You may have to
clean up the segmentation a little at the end, but that's true for any
program. Then you can save the segmentation as a 3D model or mesh.

You might download it and do a quick test segmentation, and you'll see
how straighforward it is. I had tried 3D Slicer prior to that and
couldn't get it to do anything useful. Then someone recommended
ITK-SNAP. Of course there are a few commercial apps too, but they
aren't any easier to use, and not really any more powerful than ITK,
and obviously more expensive.

Downsampling the scan is a good idea. I often do that. You can also
crop it, e.g. if it's a scan of the whole skull and you only need to
segment the endocranium. I like IrfanView which can do batch crop and
resize and has a DICOM plugin (and it's free, at least the older
versions). 0.1 mm is pretty high resolution unless you're scanning
mice!

Cheers,
Paul P.

On 2/23/23, Murat Maga mailto:muratm...@gmail.com>> wrote:
> Without the data it is hard to tell, but often those crashes are memory
> related. Memory usage during segmentation increases 8-10 folds based on the
> segmentation effect being used. So if your dataset is 2GB, you need minimum
> of 16-20GB of "available" RAM for Slicer to work properly. If you can share
> your dataset, I can take a look.
>
> Also for endocast segmentation there is no need to work with full
> resolution images. You can downsample your image (via the CropVolume) by 2,
> and then try. That will reduce your data volume by 8 folds. Your
> experiments will go faster too.
>
> The other important parameters is the size of the largest hole to plug, and
> the smoothing. Default parameters we included worked fine for large apes,
> but I am not sure for seal skulls.
>
>
>
> On Thursday, February 23, 2023 at 7:24:30 AM UTC-8 Christy Hipsley wrote:

--
You received this message because you are subscribed to the Google Groups 
"Morphmet" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
morphmet2+unsubscr...@googlegroups.com<mailto:morphmet2+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/morphmet2/CAJveYNT5LrdYjdMLhpoc_zvgj+CQw=m4kzcbgsr3ban6hb0...@mail.gmail.com<https://groups.google.com/d/msgid/morphmet2/CAJveYNT5LrdYjdMLhpoc_zvgj+CQw=m4kzcbgsr3ban6hb0...@mail.gmail.com>.

-- 
You received this message because you are subscribed to the Google Groups 
"Morphmet" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to morphmet2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/morphmet2/SY4PR01MB62848AABB3E5573CDEFCA0F4A9AB9%40SY4PR01MB6284.ausprd01.prod.outlook.com.

[jira] [Created] (KARAF-7665) Karaf Webconsole Restart does not properly restart

2023-02-01 Thread Vera Stoyanova (Jira)

Vera Stoyanova created KARAF-7665:
-

 Summary: Karaf Webconsole Restart does not properly restart
 Key: KARAF-7665
 URL: https://issues.apache.org/jira/browse/KARAF-7665
 Project: Karaf
  Issue Type: Bug
  Components: webconsole
Affects Versions: 4.4.3
Reporter: Vera Stoyanova
 Attachments: image-2023-02-01-14-17-57-256.png, karaf.log

The Restart button on [http://localhost:8181/system/console/vmstat] does not 
restart properly. 
The java process is still alive, but the webconsole no longer responds. 

1. Downloaded the Karaf 4.4.3 from the official website. 
2. Unzipped and modified the etc/users.properties
3. Started karaf and installed:

feature:install http 
feature:install webconsole

Logged in into [http://localhost:8181/system/console/vmstat] and clicked 
Restart. 
The console is attached as an image and the log file is also attached to the 
ticket. 

!image-2023-02-01-14-17-57-256.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Welcome Ben Trent as Lucene committer

2023-01-27 Thread Ignacio Vera

Congratulations Ben!

On Fri, Jan 27, 2023 at 5:08 PM Luca Cavanna  wrote:

> Welcome Ben, congratulations!
>
> On Fri, Jan 27, 2023 at 4:27 PM Ishan Chattopadhyaya <
> ichattopadhy...@gmail.com> wrote:
>
>> Welcome and congratulations, Ben!
>>
>> On Fri, Jan 27, 2023 at 8:48 PM Adrien Grand  wrote:
>> >
>> > I'm pleased to announce that Ben Trent has accepted the PMC's
>> > invitation to become a committer.
>> >
>> > Ben, the tradition is that new committers introduce themselves with a
>> > brief bio.
>> >
>> > Congratulations and welcome!
>> >
>> > --
>> > Adrien
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> > For additional commands, e-mail: dev-h...@lucene.apache.org
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>>

[Corpora-List] 1 PhD position in neural language generation

2023-01-27 Thread Vera Demberg via Corpora


*1 PhD-Position in Neural Language Generation
*

We invite applications for one PhD student position in data-to-text
natural language generation in a low resource context. The goal of the
project is to develop methods that generalize well to settings where
little training data for the domain of interest is available.

The position, to be established in thegroup "Computer Science and
Computational Linguistics" (Prof. Vera Demberg)
<https://www.uni-saarland.de/lehrstuhl/demberg.html>, is part of the E2
project of DFG-funded transregional collaborative research center on
perspicuous computing, CPEC
<https://www.perspicuous-computing.science/>. There will also be the
opportunity to closely collaborate with researchers working on the
DFG-fundedCollaborative Research Center on Information Density and
Linguistic Encoding <http://www.sfb1102.uni-saarland.de/>(SFB 1102)
<http://www.sfb1102.uni-saarland.de/>.

Candidates for this position should have a master's degree in
computational linguistics, computer science or a related discipline.
Experience with machine learning including deep learning is expected;
background and previous experience in natural language processing is
also expected. The research will be conducted in English.

Dates: *application deadline:     Feb 15, 2023*

            start date:                     spring or summer 2023

The expected duration of the PhD is 3.5 years, the position is paid
according to 75% TV-L E13, see
alsohttps://oeffentlicher-dienst.info/c/t/rechner/tv-l/west?id=tv-l-2020=12
<https://oeffentlicher-dienst.info/c/t/rechner/tv-l/west?id=tv-l-2020=12>.

The job does not come with any teaching obligation. You can however
choose to participate in teaching activities (tutoring or co-teaching).

Applicants are requested to submit their application, including a cover
letter that specifies why you would like to work on this topic and what
qualifies you for it, an academic CV, a list of academic publications,
your MSc thesis (or a current draft), copies of academic degree
certificates and names of two potential references. Please also include
a 2-page research proposal in your application which outlines how you
would approach the topic (choose one topic among multitask learning,
domain adaptation or connective generation for discourse coherence).

Saarland University <https://www.uni-saarland.de/en/home.html> is one of
the leading centres for computational linguistics and computer science
in Europe, and offers a dynamic and stimulating research environment. It
is famous for its interdisciplinary research in language, translation,
computation and cognition. The group is affiliated with both
theDepartment of Computer Science
<https://www.uni-saarland.de/fachrichtung/informatik.html>and with the
Department of Language Science and Technology
<https://www.lst.uni-saarland.de/>.
The Department of Language Science and Technology organizes about 100
research staff in ten research groups in the fields of computational
linguistics, psycholinguistics, speech processing, and corpus linguistics.

Both departments are part of the Saarland Informatics Campus
<https://saarland-informatics-campus.de/en>, which brings together 800
researchers and 2000 students from 81 countries. We collaborate closely
with the university's Department of Computer Science, the Max Planck
Institute for Informatics <https://www.mpi-inf.mpg.de/home/>, the Max
Planck Institute for Software Systems <https://www.mpi-sws.org/>, and
the German Research Center for Artificial Intelligence
<https://www.dfki.de/en/web/> (DFKI).

Our researchers and students come from all over the world, and our
primary working language is English.

Saarland University is an equal opportunity employer. Applications of
women are strongly encouraged; applications of disabled persons will be
given preferential treatment to those of other candidates with equal
qualifications.

Applications should be sent via email directly to Prof. Vera Demberg
(vera(at)coli.uni-saarland.de), quoting opening number W2229.


___
Corpora mailing list -- corpora@list.elra.info
https://list.elra.info/mailman3/postorius/lists/corpora.list.elra.info/
To unsubscribe send an email to corpora-le...@list.elra.info

Re: [VOTE] Release Lucene 9.5.0 RC1

2023-01-26 Thread Ignacio Vera

+1

SUCCESS! [0:44:15.998020]

On Thu, Jan 26, 2023 at 9:19 AM Jan Høydahl  wrote:

> +1
>
> SUCCESS! [0:36:32.191785]
>
> Jan
>
> 25. jan. 2023 kl. 19:43 skrev Luca Cavanna :
>
> Please vote for release candidate 1 for Lucene 9.5.0
>
> The artifacts can be downloaded from:
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.5.0-RC1-rev-13803aa6ea7fee91f798cfeded4296182ac43a21
>
> You can run the smoke tester directly with this command:
>
> python3 -u dev-tools/scripts/smokeTestRelease.py \
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.5.0-RC1-rev-13803aa6ea7fee91f798cfeded4296182ac43a21
>
> The vote will be open for at least 72 hours i.e. until 2023-01-28 19:00
> UTC.
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Here is my +1
>
>
>

Unsuscribe me

2023-01-19 Thread Isma Santacruz Vera

Hello
Could you please unsubscribe me?

Thanks

Re: Lucene 9.5.0 release

2023-01-16 Thread Ignacio Vera

+1

On Mon, Jan 16, 2023 at 12:58 PM Alan Woodward  wrote:

> +1, thanks Luca!
>
> On 13 Jan 2023, at 09:54, Luca Cavanna  wrote:
>
> Hi all,
> I'd like to propose that we release Lucene 9.5.0. There is a decent amount
> of changes that would go into it looking at the github milestone:
> https://github.com/apache/lucene/milestone/4 . I'd volunteer to be the
> release manager. There is one PR open listed for the 9.5 milestone:
> https://github.com/apache/lucene/pull/11873 . Is this something that we
> do want to address before we release? Is anybody aware of outstanding work
> that we would like to include or known blocker issues that are not listed
> in the 9.5 milestone?
>
> Cheers
> Luca
>
>
>
>
>
>

Access to Jira

2022-11-23 Thread Vera Cardoso

Hello,

Our team is working with Calcite and during our developments we found some
issues that we would like to report on Jira and also contribute to
the project evolution and bug fixing.

To be able to do that we would like to have an account on the Jira platform
(https://issues.apache.org/jira/browse/CALCITE).

Would it be possible for you to create an account for our team? The email
address could be `rd.dna.datafabric.j...@outsystems.com` or
vera.card...@outsystems.com.

Best regards,

Vera Cardoso | Lead Software Engineer

m: +351 963 153 663

The High-Performance Low-Code Platform - Empowering every company to
innovate through software.

<https://www.outsystems.com/?utm_source=signature_medium=email_campaign=sign>

Re: [VOTE] Release Lucene 9.4.2 RC1

2022-11-17 Thread Ignacio Vera

SUCCESS! [0:46:39.842784]


+1

On Thu, Nov 17, 2022 at 3:18 PM Adrien Grand  wrote:

> Please vote for release candidate 1 for Lucene 9.4.2
>
> The artifacts can be downloaded from:
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
>
> You can run the smoke tester directly with this command:
>
> python3 -u dev-tools/scripts/smokeTestRelease.py \
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.2-RC1-rev-858d9b437047a577fa9457089afff43eefa461db
>
> The vote will be open for at least 72 hours i.e. until 2022-11-20 15:00
> UTC.
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Here is my +1.
>
> --
> Adrien
>

Re: [ANNOUNCE] Apache Lucene 9.4.1 released

2022-11-02 Thread Ignacio Vera

Thanks Uwe! I don't remember seeing that step on the release manager, I
wonder if it is missing.

On Fri, Oct 28, 2022 at 4:32 PM Uwe Schindler  wrote:

> Hi,
>
> I just pressed the release button next to the Tag on Github. You missed to
> do that. Now it shows 9.4.1 on Github's Lucene homepage.
>
> Uwe
>
> Am 24.10.2022 um 14:30 schrieb Ignacio Vera:
>
> The Lucene PMC is pleased to announce the release of Apache Lucene 9.4.1.
>
>
> Apache Lucene is a high-performance, full-featured search engine library
> written entirely in Java. It is a technology suitable for nearly any
> application that requires structured search, full-text search, faceting,
> nearest-neighbor search across high-dimensionality vectors, spell
> correction or query suggestions.
>
>
> This release contains numerous bug fixes, optimizations, and improvements,
> some of which are highlighted below. The release is available for immediate
> download at:
>
>
>   <https://lucene.apache.org/core/downloads.html>
>
>
> ### Lucene 9.4.1 Release Highlights:
>
>
>  * When reading large segments, the kNN vectors format could fail with a
> validation error, preventing further writes or searches on the index. This
> bug is now fixed. Only version 9.4.0 was affected, so it is recommended to
> skip 9.4.0 if you are using kNN vectors.
>
>
> Please read CHANGES.txt for a full list of changes:
>
>
>   <https://lucene.apache.org/core/9_4_1/changes/Changes.html>
>
>
>
> Note: The Apache Software Foundation uses an extensive mirroring network
> for
>
> distributing releases. It is possible that the mirror you are using may
> not have
>
> replicated the release yet. If that is the case, please try another mirror.
>
> This also applies to Maven access.
>
> --
> Uwe Schindler
> Achterdiek 19, D-28357 Bremenhttps://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>

Re: [JENKINS] Lucene » Lucene-Check-9.4 - Build # 509 - Failure!

2022-10-25 Thread Ignacio Vera

I think the problem here is that at the point of running those commands I
had lost trust in the release wizard and I was running the commands
manually. The instructions for those steps do not contain running tidy
(maybe we should add them there too).

One of the problems at the moment in the release wizard is that any step
that involves running a gradle task on main branch fails because it
requires java 17 and we run all commands with java 11. I think that should
be addressed, those steps were missing for the 9.4.0 release and I fixed
them too.

On Mon, Oct 24, 2022 at 7:57 PM Dawid Weiss  wrote:

>
> What's weird is that tidy should have been called from within the release
> wizard - it was added in this issue.
>
> https://github.com/apache/lucene/pull/11748
>
> Have I missed something obvious here?
>
> Dawid
>
> On Mon, Oct 24, 2022 at 5:28 PM Ignacio Vera  wrote:
>
>> I pushed a fix for this spotless error.
>>
>> On Mon, Oct 24, 2022 at 4:17 PM Apache Jenkins Server <
>> jenk...@builds.apache.org> wrote:
>>
>>> Build: https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-9.4/509/
>>>
>>> All tests passed
>>>
>>> Build Log:
>>> [...truncated 1292 lines...]
>>> BUILD FAILED in 19m 30s
>>> 797 actionable tasks: 797 executed
>>> Build step 'Invoke Gradle script' changed build result to FAILURE
>>> Build step 'Invoke Gradle script' marked build as failure
>>> Archiving artifacts
>>> Recording test results
>>> [Checks API] No suitable checks publisher found.
>>> Email was triggered for: Failure - Any
>>> Sending email for trigger: Failure - Any
>>>
>>> -
>>> To unsubscribe, e-mail: builds-unsubscr...@lucene.apache.org
>>> For additional commands, e-mail: builds-h...@lucene.apache.org
>>
>>

Re: [JENKINS] Lucene » Lucene-Check-9.4 - Build # 509 - Failure!

2022-10-24 Thread Ignacio Vera

I pushed a fix for this spotless error.

On Mon, Oct 24, 2022 at 4:17 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build: https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-9.4/509/
>
> All tests passed
>
> Build Log:
> [...truncated 1292 lines...]
> BUILD FAILED in 19m 30s
> 797 actionable tasks: 797 executed
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Archiving artifacts
> Recording test results
> [Checks API] No suitable checks publisher found.
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
>
> -
> To unsubscribe, e-mail: builds-unsubscr...@lucene.apache.org
> For additional commands, e-mail: builds-h...@lucene.apache.org

[ANNOUNCE] Apache Lucene 9.4.1 released

2022-10-24 Thread Ignacio Vera

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The Lucene PMC is pleased to announce the release of Apache Lucene 9.4.1.

Apache Lucene is a high-performance, full-featured search engine library
written entirely in Java. It is a technology suitable for nearly any
application that requires structured search, full-text search, faceting,
nearest-neighbor search across high-dimensionality vectors, spell
correction or query suggestions.

This release contains numerous bug fixes, optimizations, and improvements,
some of which are highlighted below. The release is available for immediate
download at:

  

### Lucene 9.4.1 Release Highlights:

 * When reading large segments, the kNN vectors format could fail with a
validation error, preventing further writes or searches on the index. This
bug is now fixed. Only version 9.4.0 was affected, so it is recommended to
skip 9.4.0 if you are using kNN vectors.

Please read CHANGES.txt for a full list of changes:

  

Note: The Apache Software Foundation uses an extensive mirroring network
for
distributing releases. It is possible that the mirror you are using may not
have
replicated the release yet. If that is the case, please try another mirror.
This also applies to Maven access.
-BEGIN PGP SIGNATURE-
Version: FlowCrypt Email Encryption 8.3.8
Comment: Seamlessly send and receive encrypted email

wsFzBAEBCgAGBQJjVoWtACEJEF4dAqx8+ZrcFiEE1f+9BL/OkxIhPcgcXh0C
rHz5mtxD4g/+KNiccDAtUf6sLpmnNyKkpBUnb1tPRGs+leK700hLIDtgKDg0
vw49bmUaQqvz4QeauYX6eFknkpnMoyNIMScbSs/TBMD3z5LJCXv6QPVtoFTJ
p55ZWpG+W+z0GjBJks9HSKiZRuryEFePUYnCrrqO/vejxOstV3W15Vk0I9Nc
K7Nyg7QPRh1hUbldLzIKjhC3m27nQS+TN6nQdoAmMRmH1a/VL6L/wxugXIQF
H8d62GK6G6k2bZob+NUC6pT5d0WNmgnOQEggvu470uWB+W3zBVLpfALRjNIZ
Gxq+kOHDLff//lDa6oRwvre8pxpeahuKWJ+ipQXms+PQ2xdBPJT6ztl+KPvc
0UqneS48tiF7vv9EiCpgrJ2bk9sAlQ0DSlN5RadtuaeYIr7j+g8QFVfytCEu
SZP8NVcGBLK2S+HRCucmRhZsfP8XCXGJSNQ9dRVjE9/GMtww5rlpJDFAouVZ
DR3er4+mFP3JZ2XmhDXHwB8Stl7DFrZyYoqqIS/E2JlUFusmuGj4B2MSlmpl
ldVuD3M9b+us2ax9xTlLqeFvshinPNBLGZCFwDHapjRdwNOkml9YNjW1WPaT
gQGsDus1A81MuhIF751n2khAgo36iE/h2AbKZSrfTLyVEgfKawTDkeVNfZJT
In22bPkTrV9VtavtR5A1i1k1/7J05YDMsok=
=hmtf
-END PGP SIGNATURE-

[ANNOUNCE] Apache Lucene 9.4.1 released

2022-10-24 Thread Ignacio Vera

The Lucene PMC is pleased to announce the release of Apache Lucene 9.4.1.


Apache Lucene is a high-performance, full-featured search engine library
written entirely in Java. It is a technology suitable for nearly any
application that requires structured search, full-text search, faceting,
nearest-neighbor search across high-dimensionality vectors, spell
correction or query suggestions.


This release contains numerous bug fixes, optimizations, and improvements,
some of which are highlighted below. The release is available for immediate
download at:


  


### Lucene 9.4.1 Release Highlights:


 * When reading large segments, the kNN vectors format could fail with a
validation error, preventing further writes or searches on the index. This
bug is now fixed. Only version 9.4.0 was affected, so it is recommended to
skip 9.4.0 if you are using kNN vectors.


Please read CHANGES.txt for a full list of changes:


  



Note: The Apache Software Foundation uses an extensive mirroring network for

distributing releases. It is possible that the mirror you are using may not
have

replicated the release yet. If that is the case, please try another mirror.

This also applies to Maven access.

[ANNOUNCE] Apache Lucene 9.4.1 released

2022-10-24 Thread Ignacio Vera

The Lucene PMC is pleased to announce the release of Apache Lucene 9.4.1.


Apache Lucene is a high-performance, full-featured search engine library
written entirely in Java. It is a technology suitable for nearly any
application that requires structured search, full-text search, faceting,
nearest-neighbor search across high-dimensionality vectors, spell
correction or query suggestions.


This release contains numerous bug fixes, optimizations, and improvements,
some of which are highlighted below. The release is available for immediate
download at:


  


### Lucene 9.4.1 Release Highlights:


 * When reading large segments, the kNN vectors format could fail with a
validation error, preventing further writes or searches on the index. This
bug is now fixed. Only version 9.4.0 was affected, so it is recommended to
skip 9.4.0 if you are using kNN vectors.


Please read CHANGES.txt for a full list of changes:


  



Note: The Apache Software Foundation uses an extensive mirroring network for

distributing releases. It is possible that the mirror you are using may not
have

replicated the release yet. If that is the case, please try another mirror.

This also applies to Maven access.

Re: Bugfix release Lucene 9.4.1

2022-10-24 Thread Ignacio Vera

I push the following commit to the lucene-site which seems to fix the
issue. New versions of Markdown seem to break the build.

https://github.com/apache/lucene-site/commit/dc74048f65395ce853a7d93d9b4750db073973df

On Mon, Oct 24, 2022 at 1:19 PM Ignacio Vera  wrote:

> Hello,
>
> I am currently stuck on the release on the lucene site. I think I have
> everything in place but it seems it is not building properly so when I look
> into staging I see nothing:
>
> https://lucene.staged.apache.org/
>
> I have tried to build it locally without success and have no clue how to
> debug it further. Hopefully someone can help here. I see in the logs many
> failures like:
>
> WARNING: Feeds generated without SITEURL set properly may not be valid
> ERROR: Could not process
> pylucene/pylucene_news/2020-04-29-8-3-0-available.md
> | module 'markdown' has no attribute 'version_info'
> ERROR: Could not process core/core_news/2018-06-27-7-4-0-available.md
> | module 'markdown' has no attribute 'version_info'
> ERROR: Could not process core/core_news/2014-04-15-4-7-2-available.md
> | module 'markdown' has no attribute 'version_info'
> ERROR: Could not process core/core_news/2020-03-24-8-5-0-available.md
> | module 'markdown' has no attribute 'version_info'
> ERROR: Could not process core/core_news/2020-10-07-8-6-3-available.md
> | module 'markdown' has no attribute 'version_info'
>
>
> Thanks,
>
> Ignacio
>
>
>
>
>
>
> On Thu, Oct 20, 2022 at 4:14 PM Ignacio Vera  wrote:
>
>> Hello,
>>
>> I spoke with Julie and I agree to take over the release manager duties
>> for this release. I will shortly astart the vote.
>>
>> In the meanwhile, here are the release notes that Julie had already
>> prepared for review:
>>
>> https://cwiki.apache.org/confluence/display/LUCENE/Release+Notes+9.4.1
>>
>> On Wed, Oct 19, 2022 at 8:54 PM Julie Tibshirani 
>> wrote:
>>
>>> I am now preparing for a bugfix release from branch branch_9_4
>>>
>>> Please observe the normal rules for committing to this branch:
>>>
>>> * Before committing to the branch, reply to this thread and argue
>>>   why the fix needs backporting and how long it will take.
>>> * All issues accepted for backporting should be marked with 9.4.1
>>>   in GitHub, and issues that should delay the release must be marked as
>>> Blocker
>>> * All patches that are intended for the branch should first be committed
>>>   to the unstable branch, merged into the stable branch, and then into
>>>   the current release branch.
>>> * Only issues with Milestone version 9.4.1 and priority "Blocker" will
>>> delay
>>>   a release candidate build.
>>>
>>> As I mentioned yesterday, I plan to merge this important fix into
>>> branch_9_4: https://github.com/apache/lucene/pull/11861. I didn't hear
>>> from people about other changes that were important to backport and
>>> release. So my plan is to start building a release candidate
>>> soon, hopefully having it ready in a few hours, by the end of my day.
>>>
>>> Julie
>>>
>>

Re: Bugfix release Lucene 9.4.1

2022-10-24 Thread Ignacio Vera

Hello,

I am currently stuck on the release on the lucene site. I think I have
everything in place but it seems it is not building properly so when I look
into staging I see nothing:

https://lucene.staged.apache.org/

I have tried to build it locally without success and have no clue how to
debug it further. Hopefully someone can help here. I see in the logs many
failures like:

WARNING: Feeds generated without SITEURL set properly may not be valid
ERROR: Could not process
pylucene/pylucene_news/2020-04-29-8-3-0-available.md
| module 'markdown' has no attribute 'version_info'
ERROR: Could not process core/core_news/2018-06-27-7-4-0-available.md
| module 'markdown' has no attribute 'version_info'
ERROR: Could not process core/core_news/2014-04-15-4-7-2-available.md
| module 'markdown' has no attribute 'version_info'
ERROR: Could not process core/core_news/2020-03-24-8-5-0-available.md
| module 'markdown' has no attribute 'version_info'
ERROR: Could not process core/core_news/2020-10-07-8-6-3-available.md
| module 'markdown' has no attribute 'version_info'


Thanks,

Ignacio






On Thu, Oct 20, 2022 at 4:14 PM Ignacio Vera  wrote:

> Hello,
>
> I spoke with Julie and I agree to take over the release manager duties for
> this release. I will shortly astart the vote.
>
> In the meanwhile, here are the release notes that Julie had already
> prepared for review:
>
> https://cwiki.apache.org/confluence/display/LUCENE/Release+Notes+9.4.1
>
> On Wed, Oct 19, 2022 at 8:54 PM Julie Tibshirani 
> wrote:
>
>> I am now preparing for a bugfix release from branch branch_9_4
>>
>> Please observe the normal rules for committing to this branch:
>>
>> * Before committing to the branch, reply to this thread and argue
>>   why the fix needs backporting and how long it will take.
>> * All issues accepted for backporting should be marked with 9.4.1
>>   in GitHub, and issues that should delay the release must be marked as
>> Blocker
>> * All patches that are intended for the branch should first be committed
>>   to the unstable branch, merged into the stable branch, and then into
>>   the current release branch.
>> * Only issues with Milestone version 9.4.1 and priority "Blocker" will
>> delay
>>   a release candidate build.
>>
>> As I mentioned yesterday, I plan to merge this important fix into
>> branch_9_4: https://github.com/apache/lucene/pull/11861. I didn't hear
>> from people about other changes that were important to backport and
>> release. So my plan is to start building a release candidate
>> soon, hopefully having it ready in a few hours, by the end of my day.
>>
>> Julie
>>
>

[RESULT] [VOTE] Release Lucene 9.4.1 RC1

2022-10-23 Thread Ignacio Vera

It's been >72h since the vote was initiated and the result is:


+1  6  (6 binding)

 0  0

-1  0


This vote has PASSED

[VOTE] Release Lucene 9.4.1 RC1

2022-10-20 Thread Ignacio Vera

Please vote for release candidate 1 for Lucene 9.4.1


The artifacts can be downloaded from:

https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.1-RC1-rev-810817993e0956e63e29906e78a245949501b77d


You can run the smoke tester directly with this command:


python3 -u dev-tools/scripts/smokeTestRelease.py \

https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.1-RC1-rev-810817993e0956e63e29906e78a245949501b77d


The vote will be open for at least 72 hours i.e. until 2022-10-23 15:00 UTC.


[ ] +1  approve

[ ] +0  no opinion

[ ] -1  disapprove (and reason why)


Here is my +1

Re: Bugfix release Lucene 9.4.1

2022-10-20 Thread Ignacio Vera

Hello,

I spoke with Julie and I agree to take over the release manager duties for
this release. I will shortly astart the vote.

In the meanwhile, here are the release notes that Julie had already
prepared for review:

https://cwiki.apache.org/confluence/display/LUCENE/Release+Notes+9.4.1

On Wed, Oct 19, 2022 at 8:54 PM Julie Tibshirani 
wrote:

> I am now preparing for a bugfix release from branch branch_9_4
>
> Please observe the normal rules for committing to this branch:
>
> * Before committing to the branch, reply to this thread and argue
>   why the fix needs backporting and how long it will take.
> * All issues accepted for backporting should be marked with 9.4.1
>   in GitHub, and issues that should delay the release must be marked as
> Blocker
> * All patches that are intended for the branch should first be committed
>   to the unstable branch, merged into the stable branch, and then into
>   the current release branch.
> * Only issues with Milestone version 9.4.1 and priority "Blocker" will
> delay
>   a release candidate build.
>
> As I mentioned yesterday, I plan to merge this important fix into
> branch_9_4: https://github.com/apache/lucene/pull/11861. I didn't hear
> from people about other changes that were important to backport and
> release. So my plan is to start building a release candidate
> soon, hopefully having it ready in a few hours, by the end of my day.
>
> Julie
>

Re: Welcome Luca Cavanna as Lucene committer

2022-10-06 Thread Ignacio Vera

Welcome Luca!

On Thu, Oct 6, 2022 at 11:31 AM Bruno Roustant 
wrote:

> Welcome!
>
> Le jeu. 6 oct. 2022 à 11:20, Michael Sokolov  a
> écrit :
>
>> Welcome Luca!
>>
>> On Thu, Oct 6, 2022, 1:05 AM 陆徐刚  wrote:
>>
>>> Welcome！
>>>
>>> Xugang
>>>
>>> https://github.com/LuXugang
>>>
>>> On Oct 6, 2022, at 13:59, Mikhail Khludnev  wrote:
>>>
>>> 
>>> Welcome, Luca.
>>>
>>> On Wed, Oct 5, 2022 at 8:04 PM Adrien Grand  wrote:
>>>
 I'm pleased to announce that Luca Cavanna has accepted the PMC's
 invitation to become a committer.

 Luca, the tradition is that new committers introduce themselves with a
 brief bio.

 Congratulations and welcome!

 --
 Adrien

>>>
>>>
>>> --
>>> Sincerely yours
>>> Mikhail Khludnev
>>>
>>>

[WikiEL] Support our project? WMF Anti-disinformation crowdsourcing

2022-09-30 Thread Valentina Vera-Quiroz

Dear Community,



I hope this email finds you well and that you don’t mind me reaching out.
I’m Valentina from the Global Advocacy team at WMF. I’m working with
Costanza, our Anti-Disinformation Strategy Lead, to help Wikimedians
counter disinformation. We’re reaching out to learn about your experience.

If you are working on disinformation or have combated disinformation on any
Wikimedia project in the past, we want to learn from you.  This
conversation would be part of a larger project.

Context: We’re speaking with volunteers and community members to understand
what initiatives, activities, and tools you may have already deployed to
counter disinformation. We want to crowdsource best practices and help you
amplify them so that they can be helpful to other members of our community.
The goal is to create a public map
<https://diff.wikimedia.org/2022/08/09/help-wikimedia-counter-disinformation/>
of existing activities and tools, and in the process to better understand
what each community needs and how we can support and connect.

If you have experience with disinformation across Wikimedia platforms,
would you have 30 minutes in the next two weeks to speak with us?

Please extend this invitation to anyone in your network, or let us know if
there’s someone else you think we should contact.

Looking forward to scheduling time to talk,


Valentina

-- 

Valentina Vera Quiroz

Human Rights, Tech, and Policy Fellow

Wikimedia Foundation

1 Montgomery Street, Suite 1600

San Francisco, CA 94104

vveraquiroz-...@wikimedia.org


NOTICE: This message might have confidential or legally privileged
information in it. If you have received this message by accident, please
delete it and let us know about the mistake. For legal reasons, I may only
serve as a legal fellow for the Wikimedia Foundation. This means I may not
give legal advice to or serve as a lawyer for community members,
volunteers, or staff members in their personal capacity.
___
WikiEL mailing list -- wikiel@lists.wikimedia.org
To unsubscribe send an email to wikiel-le...@lists.wikimedia.org

[Wikimediaeg-l] Support our project? WMF Anti-disinformation crowdsourcing

2022-09-28 Thread Valentina Vera-Quiroz

Dear Community,



I hope this email finds you well and that you don’t mind me reaching out.
I’m Valentina from the Global Advocacy team at WMF. I’m working with
Costanza, our Anti-Disinformation Strategy Lead, to help Wikimedians
counter disinformation. We’re reaching out to learn about your experience.

If you are working on disinformation or have combated disinformation on any
Wikimedia project in the past, we want to learn from you.  This
conversation would be part of a larger project.

Context: We’re speaking with volunteers and community members to understand
what initiatives, activities, and tools you may have already deployed to
counter disinformation. We want to crowdsource best practices and help you
amplify them so that they can be helpful to other members of our community.
The goal is to create a public map
<https://diff.wikimedia.org/2022/08/09/help-wikimedia-counter-disinformation/>
of existing activities and tools, and in the process to better understand
what each community needs and how we can support and connect.

If you have experience with disinformation across Wikimedia platforms,
would you have 30 minutes in the next two weeks to speak with us?

Please extend this invitation to anyone in your network, or let us know if
there’s someone else you think we should contact.

Looking forward to scheduling time to talk,


Valentina

-- 

Valentina Vera Quiroz

Human Rights, Tech, and Policy Fellow

Wikimedia Foundation

1 Montgomery Street, Suite 1600

San Francisco, CA 94104

vveraquiroz-...@wikimedia.org


NOTICE: This message might have confidential or legally privileged
information in it. If you have received this message by accident, please
delete it and let us know about the mistake. For legal reasons, I may only
serve as a legal fellow for the Wikimedia Foundation. This means I may not
give legal advice to or serve as a lawyer for community members,
volunteers, or staff members in their personal capacity.
___
WikimediaEG-l mailing list -- wikimediaeg-l@lists.wikimedia.org
To unsubscribe send an email to wikimediaeg-l-le...@lists.wikimedia.org

Re: [VOTE] Release Lucene 9.4.0 RC3

2022-09-28 Thread Ignacio Vera

+1 (binding)


SUCCESS! [0:53:18.788514]

On Wed, Sep 28, 2022 at 6:50 AM Patrick Zhai  wrote:

> +1 (non-binding)
>
> SUCCESS! [0:57:17.821452]
>
> On Tue, Sep 27, 2022 at 3:32 PM Michael McCandless <
> luc...@mikemccandless.com> wrote:
>
>> +1, smoke tester:
>>
>> SUCCESS! [0:26:01.696388]
>>
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>>
>> On Tue, Sep 27, 2022 at 3:45 PM Anshum Gupta 
>> wrote:
>>
>>> +1 (binding)
>>>
>>> Smoketester is happy!
>>> SUCCESS! [0:54:06.589484]
>>>
>>> On Tue, Sep 27, 2022 at 6:15 AM Michael Sokolov 
>>> wrote:
>>>
 Please vote for release candidate 3 for Lucene 9.4.0

 The artifacts can be downloaded from:

 https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.0-RC3-rev-d2e22e18c6c92b6a6ba0bbc26d78b5e82832f956

 You can run the smoke tester directly with this command:

 python3 -u dev-tools/scripts/smokeTestRelease.py \

 https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.0-RC3-rev-d2e22e18c6c92b6a6ba0bbc26d78b5e82832f956

 The vote will be open for at least 72 hours i.e. until 2022-09-30 14:00
 UTC.

 [ ] +1  approve
 [ ] +0  no opinion
 [ ] -1  disapprove (and reason why)

 Here is my +1

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


>>>
>>> --
>>> Anshum Gupta
>>>
>>

Re: [VOTE] Release Lucene 9.4.0 RC2

2022-09-27 Thread Ignacio Vera

Thank you Mike, sorry for all the extra work!

On Tue, Sep 27, 2022 at 3:14 PM Michael Sokolov  wrote:

> OK, well I am glad we were able to fix quickly.
>
> This vote is failed; I've re-spun RC3 and will start a new vote thread
>
> On Tue, Sep 27, 2022 at 5:52 AM Uwe Schindler  wrote:
> >
> > Hi,
> >
> > I also added the small build system changes and the localSettings fix
> for Smoketester to make Robert happy with validating release :-)
> >
> > Uwe
> >
> > Am 27.09.2022 um 10:59 schrieb Ignacio Vera:
> >
> > I pushed a fix to all relevant branches:
> https://github.com/apache/lucene/pull/11825
> >
> >
> >
> > On Tue, Sep 27, 2022 at 10:44 AM Anshum Gupta 
> wrote:
> >>
> >> Thanks Ignacio for noticing and reporting that. I agree with Uwe, it
> makes sense to cancel this vote and get the fix in.
> >>
> >> Thank you for being patient, Mike :)
> >>
> >> On Tue, Sep 27, 2022 at 1:20 AM Uwe Schindler  wrote:
> >>>
> >>> Hi,
> >>>
> >>> that's too bad! As not many have ran smoke tester, I think it may be a
> good idea to now stop the release.
> >>>
> >>> If we respin, I will backport some small build system fixes like
> support for Eclipse and Smoketester bootup (regarding MR-JAR) also to the
> 9.4 branch. But that's not urgent.
> >>>
> >>> Uwe
> >>>
> >>> Am 27.09.2022 um 10:01 schrieb Ignacio Vera:
> >>>
> >>> Hi,
> >>>
> >>> I just noticed an important regression on polygon queries using the
> LatLonPoint field, see https://github.com/apache/lucene/issues/11824.
> >>>
> >>> It feels like an important regression so it might be worth a
> respinning.  Sorry about that.
> >>>
> >>>
> >>> On Mon, Sep 26, 2022 at 10:30 PM Anshum Gupta 
> wrote:
> >>>>
> >>>> +1 (binding)
> >>>>
> >>>> Smoke tests passed and I tried out basic indexing and search.
> >>>> SUCCESS! [0:59:09.751008]
> >>>>
> >>>> Thanks for your effort Mike, and everyone else.
> >>>>
> >>>> On Mon, Sep 26, 2022 at 8:47 AM Michael Sokolov 
> wrote:
> >>>>>
> >>>>> Please vote for release candidate 2 for Lucene 9.4.0
> >>>>>
> >>>>> The artifacts can be downloaded from:
> >>>>>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.0-RC2-rev-0384b4fcad7856ddc574c8b994c814a568ce6d0a
> >>>>>
> >>>>> You can run the smoke tester directly with this command:
> >>>>>
> >>>>> python3 -u dev-tools/scripts/smokeTestRelease.py \
> >>>>>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.0-RC2-rev-0384b4fcad7856ddc574c8b994c814a568ce6d0a
> >>>>>
> >>>>> The vote will be open for at least 72 hours i.e. until 2022-09-29
> 16:00 UTC.
> >>>>>
> >>>>> [ ] +1  approve
> >>>>> [ ] +0  no opinion
> >>>>> [ ] -1  disapprove (and reason why)
> >>>>>
> >>>>> Here is my +1
> >>>>>
> >>>>> -
> >>>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> >>>>> For additional commands, e-mail: dev-h...@lucene.apache.org
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Anshum Gupta
> >>>
> >>> --
> >>> Uwe Schindler
> >>> Achterdiek 19, D-28357 Bremen
> >>> https://www.thetaphi.de
> >>> eMail: u...@thetaphi.de
> >>
> >>
> >>
> >> --
> >> Anshum Gupta
> >
> > --
> > 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: [VOTE] Release Lucene 9.4.0 RC2

2022-09-27 Thread Ignacio Vera

I pushed a fix to all relevant branches:
https://github.com/apache/lucene/pull/11825



On Tue, Sep 27, 2022 at 10:44 AM Anshum Gupta 
wrote:

> Thanks Ignacio for noticing and reporting that. I agree with Uwe, it makes
> sense to cancel this vote and get the fix in.
>
> Thank you for being patient, Mike :)
>
> On Tue, Sep 27, 2022 at 1:20 AM Uwe Schindler  wrote:
>
>> Hi,
>>
>> that's too bad! As not many have ran smoke tester, I think it may be a
>> good idea to now stop the release.
>>
>> If we respin, I will backport some small build system fixes like support
>> for Eclipse and Smoketester bootup (regarding MR-JAR) also to the 9.4
>> branch. But that's not urgent.
>>
>> Uwe
>> Am 27.09.2022 um 10:01 schrieb Ignacio Vera:
>>
>> Hi,
>>
>> I just noticed an important regression on polygon queries using the
>> LatLonPoint field, see https://github.com/apache/lucene/issues/11824.
>>
>> It feels like an important regression so it might be worth a respinning.
>> Sorry about that.
>>
>>
>> On Mon, Sep 26, 2022 at 10:30 PM Anshum Gupta 
>> wrote:
>>
>>> +1 (binding)
>>>
>>> Smoke tests passed and I tried out basic indexing and search.
>>> SUCCESS! [0:59:09.751008]
>>>
>>> Thanks for your effort Mike, and everyone else.
>>>
>>> On Mon, Sep 26, 2022 at 8:47 AM Michael Sokolov 
>>> wrote:
>>>
>>>> Please vote for release candidate 2 for Lucene 9.4.0
>>>>
>>>> The artifacts can be downloaded from:
>>>>
>>>> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.0-RC2-rev-0384b4fcad7856ddc574c8b994c814a568ce6d0a
>>>>
>>>> You can run the smoke tester directly with this command:
>>>>
>>>> python3 -u dev-tools/scripts/smokeTestRelease.py \
>>>>
>>>> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.0-RC2-rev-0384b4fcad7856ddc574c8b994c814a568ce6d0a
>>>>
>>>> The vote will be open for at least 72 hours i.e. until 2022-09-29 16:00
>>>> UTC.
>>>>
>>>> [ ] +1  approve
>>>> [ ] +0  no opinion
>>>> [ ] -1  disapprove (and reason why)
>>>>
>>>> Here is my +1
>>>>
>>>> -
>>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>>>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>>>
>>>>
>>>
>>> --
>>> Anshum Gupta
>>>
>> --
>> Uwe Schindler
>> Achterdiek 19, D-28357 Bremenhttps://www.thetaphi.de
>> eMail: u...@thetaphi.de
>>
>>
>
> --
> Anshum Gupta
>

Re: [VOTE] Release Lucene 9.4.0 RC2

2022-09-27 Thread Ignacio Vera

Hi,

I just noticed an important regression on polygon queries using the
LatLonPoint field, see https://github.com/apache/lucene/issues/11824.

It feels like an important regression so it might be worth a respinning.
Sorry about that.


On Mon, Sep 26, 2022 at 10:30 PM Anshum Gupta 
wrote:

> +1 (binding)
>
> Smoke tests passed and I tried out basic indexing and search.
> SUCCESS! [0:59:09.751008]
>
> Thanks for your effort Mike, and everyone else.
>
> On Mon, Sep 26, 2022 at 8:47 AM Michael Sokolov 
> wrote:
>
>> Please vote for release candidate 2 for Lucene 9.4.0
>>
>> The artifacts can be downloaded from:
>>
>> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.0-RC2-rev-0384b4fcad7856ddc574c8b994c814a568ce6d0a
>>
>> You can run the smoke tester directly with this command:
>>
>> python3 -u dev-tools/scripts/smokeTestRelease.py \
>>
>> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.0-RC2-rev-0384b4fcad7856ddc574c8b994c814a568ce6d0a
>>
>> The vote will be open for at least 72 hours i.e. until 2022-09-29 16:00
>> UTC.
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> Here is my +1
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>>
>
> --
> Anshum Gupta
>

Re: [VOTE] Release Lucene 9.4.0 RC1

2022-09-22 Thread Ignacio Vera

+1


SUCCESS! [0:46:00.508949]

On Thu, Sep 22, 2022 at 9:53 AM Adrien Grand  wrote:

> +1 SUCCESS! [0:45:35.275017]
>
> On Wed, Sep 21, 2022 at 9:19 PM Michael McCandless <
> luc...@mikemccandless.com> wrote:
>
>> +1
>>
>>
>> SUCCESS! [0:27:16.514391]
>>
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>>
>> On Wed, Sep 21, 2022 at 2:32 PM Dawid Weiss 
>> wrote:
>>
>>>
>>> +1.
>>> SUCCESS! [0:53:33.891603]
>>>
>>>
 Ran the smoketester with both java 11 and 17:

 SUCCESS! [2:41:19.024193]

 On Tue, Sep 20, 2022 at 10:10 PM Michael Sokolov 
 wrote:
 >
 > Please vote for release candidate 1 for Lucene 9.4.0
 >
 > The artifacts can be downloaded from:
 >
 https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.0-RC1-rev-f5d0646daa5651f2192282ac85551bca667e34f9
 >
 > You can run the smoke tester directly with this command:
 >
 > python3 -u dev-tools/scripts/smokeTestRelease.py \
 >
 https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.0-RC1-rev-f5d0646daa5651f2192282ac85551bca667e34f9
 >
 > The vote will be open for at least 72 hours i.e. until 2022-09-24
 02:00 UTC.
 >
 > [ ] +1  approve
 > [ ] +0  no opinion
 > [ ] -1  disapprove (and reason why)
 >
 > Here is my +1
 >
 > -
 > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
 > For additional commands, e-mail: dev-h...@lucene.apache.org
 >

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


>
> --
> Adrien
>

Re: [Geoserver-users] weird contour lines when using rendering transformation for coverage view

2022-09-13 Thread Vera Green

Looks like you are essentially giving a OR logic streamif this OR this
OR this OR this draw me. You might need to change this to an AND logic
instead.

Hope this makes sense.

On Tue., Sep. 13, 2022, 1:28 p.m. Andres Trei, 
wrote:

> Hi list.
>
> I have a netcdf store that contains multiple variables. I am trying to
> serve it as a coverage view, publishing 3 variables out of a total 7. Now
> the issue comes when trying to draw contour lines for 1 of the variables in
> view. In addition to the contours that should be there, geoserver also
> renders some additional funky contours that I have no idea where they come
> from and I believe should not be there. Below is a snippet from my SLD. If
> I remove the other 2 variables from my coverage view, everything seems to
> be ok. It looks like geoserver does not respect band parameter and uses
> data from other 2 bands also to render contours (just guessing here). Don't
> see any errors in logs.
>
> 
>   
>
> 
>   data
> 
>
> 
>   band
>   0
> 
> 
>   levels
>   0.5
>   1
>   1.5
>   2
>   2.5
>   3
>   3.5
>   4
>   4.5
>   5
> 
>   
> 
>
> Some screenshots:
>
> https://drive.google.com/file/d/1heaKCnozG60EBrx-tuJaV5Dxow1FoRhc/view?usp=sharing
>
> https://drive.google.com/file/d/1pfMHjmjhGLhHqGV171UxZn7F6cbdnqKK/view?usp=sharing
>
> https://drive.google.com/file/d/1gizFNsbXlXgOOko2fxpdZRro26LwiEPD/view?usp=sharing
>
>
> A related question for the coverage view. While using ncwms extension and
> the GetTimeSeries request to extract data on map click, the request returns
> data only for the first band in coverage view, while I was assuming I would
> get for all 3 bands. Is this expected? I've built the extension myself to
> match the geoserver version. Here's the decoded request:
>
>
> http://localhost:8088/geoserver/wms?REQUEST=GetTimeSeries=WMS==true=1.3.0=image/png=21.733703613281254,58.676937672586924,22.787017822265625,59.26026554911028=824=767=2022-09-13T12:00:00.000Z/2022-09-14T03:00:00.000Z=test_ws:dmi_waves_LAYERS=test_ws:dmi_waves_FORMAT=text/csv=206=446
>
>
> Geoserver version: 2.19.2
> Java: openjdk version "1.8.0_332"
> OS: macOS 12.5.1
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Geoserver Issue

2022-08-25 Thread Vera Green

https://docs.geoserver.org/latest/en/user/production/container.html

"The standalone distributions of GeoServer include the Jetty application
server. Enable Cross-Origin Resource Sharing (CORS)
<https://enable-cors.org/> to allow JavaScript applications outside of your
own domain, or web browsers, to use GeoServer."

On Thu., Aug. 25, 2022, 9:19 a.m. Jovan Ninkovic, 
wrote:

> How to configure cors? And why is it important?
> Tnx
>
> On Thu, Aug 25, 2022 at 17:00, Vera Green
>  wrote:
> Did you configure cors?
>
> nano /opt/tomcat/latest/conf/web.xml
>
> If not google allowing cors for GeoServer.
>
> Vera
>
> On Thu., Aug. 25, 2022, 3:52 a.m. Richard Duivenvoorde, <
> rdmaili...@duif.net> wrote:
>
> IF you can reach your server from within the network your geoserver is
> running
> and NOT from outside that network (eg Geoserver in your homenetwork and
> you want to reach it from outside your home), then your router/gateway
> cannot find your 'server'
>
> Then probably on your router there is some setting to so something named
> (on my Fritzbox it is) 'Port Sharing'. It actually means that if somebody
> knocking (from outside) on your router on port 8080, that the router knows
> where/to which computer to sent the request to.
>
> NOTE you are pushing holes in your router this way, but if that is what
> you want, that is ok :-)
>
> HTH
>
> Richard Duivenvoorde
>
> On 8/25/22 11:18, Jovan Ninkovic via Geoserver-users wrote:
> > Hi everybody,
> >
> > I've set up GeoServer on my working PC.
> > What I can't figure out is how to access it with a different PC that is
> connected to a different network.
> > I've tried to open port (8080) on my router and created Inbound and
> Outbound Rules in Firewall and still nothing.
> >
> > When I am connected to the same network as the GeoServer PC i can access
> it using the address:
> > http://xxx.xxx.x.xx:8080/geoserver/web/ - where xxx.xxx.x.xx is IP
> address of GeoServer PC.
> >
> > Can anyone share the experience or help on this how to set it up?
> >
> > Best regards,
> > Jovan
> >
> >
> > ___
> > Geoserver-users mailing list
> >
> > Please make sure you read the following two resources before posting to
> this list:
> > - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> > - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
> >
> > If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
> >
> >
> > Geoserver-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
>
>
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Geoserver Issue

2022-08-25 Thread Vera Green

Did you configure cors?

nano /opt/tomcat/latest/conf/web.xml

If not google allowing cors for GeoServer.

Vera

On Thu., Aug. 25, 2022, 3:52 a.m. Richard Duivenvoorde, 
wrote:

> IF you can reach your server from within the network your geoserver is
> running
> and NOT from outside that network (eg Geoserver in your homenetwork and
> you want to reach it from outside your home), then your router/gateway
> cannot find your 'server'
>
> Then probably on your router there is some setting to so something named
> (on my Fritzbox it is) 'Port Sharing'. It actually means that if somebody
> knocking (from outside) on your router on port 8080, that the router knows
> where/to which computer to sent the request to.
>
> NOTE you are pushing holes in your router this way, but if that is what
> you want, that is ok :-)
>
> HTH
>
> Richard Duivenvoorde
>
> On 8/25/22 11:18, Jovan Ninkovic via Geoserver-users wrote:
> > Hi everybody,
> >
> > I've set up GeoServer on my working PC.
> > What I can't figure out is how to access it with a different PC that is
> connected to a different network.
> > I've tried to open port (8080) on my router and created Inbound and
> Outbound Rules in Firewall and still nothing.
> >
> > When I am connected to the same network as the GeoServer PC i can access
> it using the address:
> > http://xxx.xxx.x.xx:8080/geoserver/web/ - where xxx.xxx.x.xx is IP
> address of GeoServer PC.
> >
> > Can anyone share the experience or help on this how to set it up?
> >
> > Best regards,
> > Jovan
> >
> >
> > ___
> > Geoserver-users mailing list
> >
> > Please make sure you read the following two resources before posting to
> this list:
> > - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> > - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
> >
> > If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
> >
> >
> > Geoserver-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
>
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[jira] [Resolved] (LUCENE-10678) computing the partition point on a BKD tree merge can overflow

2022-08-11 Thread Ignacio Vera (Jira)



 [ 
https://issues.apache.org/jira/browse/LUCENE-10678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ignacio Vera resolved LUCENE-10678.
---
Fix Version/s: 9.3.1
   8.11.3
   9.4
 Assignee: Ignacio Vera
   Resolution: Fixed

> computing the partition point on a BKD tree merge can overflow
> --
>
> Key: LUCENE-10678
> URL: https://issues.apache.org/jira/browse/LUCENE-10678
> Project: Lucene - Core
>  Issue Type: Bug
>    Reporter: Ignacio Vera
>    Assignee: Ignacio Vera
>Priority: Major
> Fix For: 9.3.1, 8.11.3, 9.4
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> I just discover a bad bug in the BKD tree when doing merges. Before calling 
> the BKDTreeRadix selector we need to compute the partition point which is 
> dome multiplying two integers. If the partition point is > Integer.MAX_VALUE 
> then it will overflow.
> https://github.com/apache/lucene/blob/35ca2d79f73c6dfaf5e648fe241f7e0b37084a90/lucene/core/src/java/org/apache/lucene/util/bkd/BKDWriter.java#L2021
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Commented] (LUCENE-10678) computing the partition point on a BKD tree merge can overflow

2022-08-10 Thread Ignacio Vera (Jira)



[ 
https://issues.apache.org/jira/browse/LUCENE-10678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17578098#comment-17578098
 ] 

Ignacio Vera commented on LUCENE-10678:
---

The error from this bug looks like:
{code:java}
: partitionPoint must be >= from
    at __randomizedtesting.SeedInfo.seed([FD9FF7A242381652:E43C04A83ACC9B76]:0)
    at 
org.apache.lucene.util.bkd.BKDRadixSelector.checkArgs(BKDRadixSelector.java:140)
    at 
org.apache.lucene.util.bkd.BKDRadixSelector.select(BKDRadixSelector.java:107)
    at org.apache.lucene.util.bkd.BKDWriter.build(BKDWriter.java:2033)
    at org.apache.lucene.util.bkd.BKDWriter.finish(BKDWriter.java:974)
 {code}
 

> computing the partition point on a BKD tree merge can overflow
> --
>
> Key: LUCENE-10678
> URL: https://issues.apache.org/jira/browse/LUCENE-10678
> Project: Lucene - Core
>  Issue Type: Bug
>    Reporter: Ignacio Vera
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> I just discover a bad bug in the BKD tree when doing merges. Before calling 
> the BKDTreeRadix selector we need to compute the partition point which is 
> dome multiplying two integers. If the partition point is > Integer.MAX_VALUE 
> then it will overflow.
> https://github.com/apache/lucene/blob/35ca2d79f73c6dfaf5e648fe241f7e0b37084a90/lucene/core/src/java/org/apache/lucene/util/bkd/BKDWriter.java#L2021
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (LUCENE-10678) computing the partition point on a BKD tree merge can overflow

2022-08-10 Thread Ignacio Vera (Jira)

Ignacio Vera created LUCENE-10678:
-

 Summary: computing the partition point on a BKD tree merge can 
overflow
 Key: LUCENE-10678
 URL: https://issues.apache.org/jira/browse/LUCENE-10678
 Project: Lucene - Core
  Issue Type: Bug
Reporter: Ignacio Vera


I just discover a bad bug in the BKD tree when doing merges. Before calling the 
BKDTreeRadix selector we need to compute the partition point which is dome 
multiplying two integers. If the partition point is > Integer.MAX_VALUE then it 
will overflow.

https://github.com/apache/lucene/blob/35ca2d79f73c6dfaf5e648fe241f7e0b37084a90/lucene/core/src/java/org/apache/lucene/util/bkd/BKDWriter.java#L2021

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Resolved] (LUCENE-10673) Spatial3d fails constructing a legal bounding box

2022-08-03 Thread Ignacio Vera (Jira)



 [ 
https://issues.apache.org/jira/browse/LUCENE-10673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ignacio Vera resolved LUCENE-10673.
---
Fix Version/s: 9.4
 Assignee: Ignacio Vera
   Resolution: Fixed

> Spatial3d fails constructing a legal bounding box
> -
>
> Key: LUCENE-10673
> URL: https://issues.apache.org/jira/browse/LUCENE-10673
> Project: Lucene - Core
>  Issue Type: Bug
>  Components: modules/spatial3d
>    Reporter: Ignacio Vera
>Assignee: Ignacio Vera
>Priority: Major
> Fix For: 9.4
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The issue can be reproduced with the following test:
> {code}
>   @Test
>   public void testBBoxLatDegenerate() {
>   double minX = Geo3DUtil.fromDegrees(-180.0);
>   double maxX = Geo3DUtil.fromDegrees(-174.3758381903);
>   double minY = Geo3DUtil.fromDegrees(89.9765306711);
>   double maxY = Geo3DUtil.fromDegrees(89.9794643372);
>   assertNotNull(GeoAreaFactory.makeGeoArea(PlanetModel.SPHERE, maxY, 
> minY, minX, maxX));
>   }
> {code}
> this currently fails with the following error:
> {code}
> Cannot determine sidedness because check point is on plane.
> java.lang.IllegalArgumentException: Cannot determine sidedness because check 
> point is on plane.
>   at 
> __randomizedtesting.SeedInfo.seed([F8095E23398C1BA6:396A213B6362092D]:0)
>   at 
> org.apache.lucene.spatial3d.geom.SidedPlane.(SidedPlane.java:137)
>   at 
> org.apache.lucene.spatial3d.geom.GeoRectangle.(GeoRectangle.java:149)
>   at 
> org.apache.lucene.spatial3d.geom.GeoBBoxFactory.makeGeoBBox(GeoBBoxFactory.java:134)
>   at 
> org.apache.lucene.spatial3d.geom.GeoAreaFactory.makeGeoArea(GeoAreaFactory.java:43)
>   at 
> org.apache.lucene.spatial3d.geom.TestGeoBBox.testBBoxLonDegenerate(TestGeoBBox.java:538)
>   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)
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Updated] (LUCENE-10673) Spatial3d fails constructing a legal bounding box

2022-08-03 Thread Ignacio Vera (Jira)



 [ 
https://issues.apache.org/jira/browse/LUCENE-10673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ignacio Vera updated LUCENE-10673:
--
Component/s: modules/spatial3d

> Spatial3d fails constructing a legal bounding box
> -
>
> Key: LUCENE-10673
> URL: https://issues.apache.org/jira/browse/LUCENE-10673
> Project: Lucene - Core
>  Issue Type: Bug
>  Components: modules/spatial3d
>    Reporter: Ignacio Vera
>Priority: Major
>
> The issue can be reproduced with the following test:
> {code}
>   @Test
>   public void testBBoxLatDegenerate() {
>   double minX = Geo3DUtil.fromDegrees(-180.0);
>   double maxX = Geo3DUtil.fromDegrees(-174.3758381903);
>   double minY = Geo3DUtil.fromDegrees(89.9765306711);
>   double maxY = Geo3DUtil.fromDegrees(89.9794643372);
>   assertNotNull(GeoAreaFactory.makeGeoArea(PlanetModel.SPHERE, maxY, 
> minY, minX, maxX));
>   }
> {code}
> this currently fails with the following error:
> {code}
> Cannot determine sidedness because check point is on plane.
> java.lang.IllegalArgumentException: Cannot determine sidedness because check 
> point is on plane.
>   at 
> __randomizedtesting.SeedInfo.seed([F8095E23398C1BA6:396A213B6362092D]:0)
>   at 
> org.apache.lucene.spatial3d.geom.SidedPlane.(SidedPlane.java:137)
>   at 
> org.apache.lucene.spatial3d.geom.GeoRectangle.(GeoRectangle.java:149)
>   at 
> org.apache.lucene.spatial3d.geom.GeoBBoxFactory.makeGeoBBox(GeoBBoxFactory.java:134)
>   at 
> org.apache.lucene.spatial3d.geom.GeoAreaFactory.makeGeoArea(GeoAreaFactory.java:43)
>   at 
> org.apache.lucene.spatial3d.geom.TestGeoBBox.testBBoxLonDegenerate(TestGeoBBox.java:538)
>   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)
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[jira] [Created] (LUCENE-10673) Spatial3d fails constructing a legal bounding box

2022-08-03 Thread Ignacio Vera (Jira)

Ignacio Vera created LUCENE-10673:
-

 Summary: Spatial3d fails constructing a legal bounding box
 Key: LUCENE-10673
 URL: https://issues.apache.org/jira/browse/LUCENE-10673
 Project: Lucene - Core
  Issue Type: Bug
Reporter: Ignacio Vera


The issue can be reproduced with the following test:

{code}
  @Test
  public void testBBoxLatDegenerate() {
  double minX = Geo3DUtil.fromDegrees(-180.0);
  double maxX = Geo3DUtil.fromDegrees(-174.3758381903);
  double minY = Geo3DUtil.fromDegrees(89.9765306711);
  double maxY = Geo3DUtil.fromDegrees(89.9794643372);
  assertNotNull(GeoAreaFactory.makeGeoArea(PlanetModel.SPHERE, maxY, minY, 
minX, maxX));
  }
{code}

this currently fails with the following error:

{code}
Cannot determine sidedness because check point is on plane.
java.lang.IllegalArgumentException: Cannot determine sidedness because check 
point is on plane.
at 
__randomizedtesting.SeedInfo.seed([F8095E23398C1BA6:396A213B6362092D]:0)
at 
org.apache.lucene.spatial3d.geom.SidedPlane.(SidedPlane.java:137)
at 
org.apache.lucene.spatial3d.geom.GeoRectangle.(GeoRectangle.java:149)
at 
org.apache.lucene.spatial3d.geom.GeoBBoxFactory.makeGeoBBox(GeoBBoxFactory.java:134)
at 
org.apache.lucene.spatial3d.geom.GeoAreaFactory.makeGeoArea(GeoAreaFactory.java:43)
at 
org.apache.lucene.spatial3d.geom.TestGeoBBox.testBBoxLonDegenerate(TestGeoBBox.java:538)
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)


{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Re: [JENKINS] Lucene » Lucene-Check-9.3 - Build # 72 - Failure!

2022-07-29 Thread Ignacio Vera

I fixed this. The script that adds new versions to addVersions.java is
generating code that makes spotless nhappy.

On Fri, Jul 29, 2022 at 3:36 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build: https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-9.3/72/
>
> All tests passed
>
> Build Log:
> [...truncated 1296 lines...]
> BUILD FAILED in 20m 47s
> 796 actionable tasks: 796 executed
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Archiving artifacts
> Recording test results
> [Checks API] No suitable checks publisher found.
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
>
> -
> To unsubscribe, e-mail: builds-unsubscr...@lucene.apache.org
> For additional commands, e-mail: builds-h...@lucene.apache.org

Re: [JENKINS] Lucene » Lucene-Check-9.3 - Build # 72 - Failure!

2022-07-29 Thread Ignacio Vera

I fixed this. The script that adds new versions to addVersions.java is
generating code that makes spotless nhappy.

On Fri, Jul 29, 2022 at 3:36 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build: https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-9.3/72/
>
> All tests passed
>
> Build Log:
> [...truncated 1296 lines...]
> BUILD FAILED in 20m 47s
> 796 actionable tasks: 796 executed
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Archiving artifacts
> Recording test results
> [Checks API] No suitable checks publisher found.
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
>
> -
> To unsubscribe, e-mail: builds-unsubscr...@lucene.apache.org
> For additional commands, e-mail: builds-h...@lucene.apache.org

[ANNOUNCE] Apache Lucene 9.3.0 released

2022-07-29 Thread Ignacio Vera

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

29 July 2022 - Apache Lucene™ 9.3.0 available

The Lucene PMC is pleased to announce the release of Apache Lucene 9.3.0.

Apache Lucene is a high-performance, full-featured search engine library
written entirely in Java. It is a technology suitable for nearly any
application that requires structured search, full-text search, faceting,
nearest-neighbor search across high-dimensionality vectors, spell
correction or query suggestions.

This release contains numerous bug fixes, optimizations, and improvements,
some of which are highlighted below. The release is available for immediate
download at:
https://lucene.apache.org/core/downloads.html

Lucene 9.3.0 Release Highlights:
• Merge on full flush is enabled now by default with a timeout of
500ms.
• Add getAllChildren functionality to facets.
• Added facetsets module for high dimensional (hyper-rectangle)
faceting.
• Top-level two-clause disjunctions sorted by score now use the
block-max MAXSCORE algorithm.
• When running KnnVectorQuery with a filter, reuse the cached
filter bit set.

Please read CHANGES.txt for a full list of new features and changes:

https://lucene.apache.org/core/9_3_0/changes/Changes.html

Note: The Apache Software Foundation uses an extensive mirroring network
for
distributing releases. It is possible that the mirror you are using may not
have
replicated the release yet. If that is the case, please try another mirror.
This also applies to Maven access.
-BEGIN PGP SIGNATURE-
Version: FlowCrypt Email Encryption 8.3.1
Comment: Seamlessly send and receive encrypted email

wsFzBAEBCgAGBQJi45IEACEJEF4dAqx8+ZrcFiEE1f+9BL/OkxIhPcgcXh0C
rHz5mtxXSRAAirTjG43cOOAtFJ3lgCqGhG/7vuE9+ZGWE1eIXlwdI+acivCz
/hS7FcuDM3XsCvftkHpqpE/gA1+ESjbh/atbifX/s9cO2ZfqtShkVuVjfJCs
vmqf9aerUDSfG7BS6+BojZto0brmDPxy2ZvbjPi1Q/MhRoppLg07yA3E/FEL
mwz0PMG6INCIy1xv5EQ8bQqUkofDiCImy5KxTNdczpwwCBZ6hcEXYXHF4MtK
5YGvZJQ9Do22ZdObaXEv5tNMkbA8LN0rUUzb3wU0evu5JCKnSe+zv3QFK4rX
pZBOdq7v+Mf3V4QVLA5R2lde8PbDVbXoKKDLPb/932VRUZ17Bk23e1YOyLXs
BJY2Ih6j4HVBepvdJ6PeE7ewDTg9qbS2QapVvBX7F4IviwBeM0KFA/f6qjC9
bQsNDROkQXaPZ9mMvY1CGtcklnGe+gl0sn3r/PfSxCRMD4hVG0sFaI13vn8Q
mqY8s+/F2I3aivjk26cMXN3pGyqqJbIBpQU0ZMNz11xW0H2I1VK0C0/BKz5e
Hjw8Eu52/LMvYxkNGnu+aTguUWr0tzQkXyUHk833db+gPK04H5dxl4RAdNpq
Suu2uiiOJY41KvqWxIjHib7KNjdpzVXfOzlHNp5i8p3ezWFPE5+pbqSAtZaj
HQ4mMURUeb6oPim4WC1uLd9Ki7cuc5AS43Y=
=fT4v
-END PGP SIGNATURE-

[jira] [Updated] (LUCENE-10589) Fix corner case in TestKnnVectorQuery.testRandomWithFilter

2022-07-29 Thread Ignacio Vera (Jira)



 [ 
https://issues.apache.org/jira/browse/LUCENE-10589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ignacio Vera updated LUCENE-10589:
--
Fix Version/s: 9.4
   (was: 9.3)

> Fix corner case in TestKnnVectorQuery.testRandomWithFilter
> --
>
> Key: LUCENE-10589
> URL: https://issues.apache.org/jira/browse/LUCENE-10589
> Project: Lucene - Core
>  Issue Type: Improvement
>Reporter: Tomoko Uchida
>Priority: Minor
> Fix For: 10.0 (main), 9.4
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> {{TestKnnVectorQuery.testRandomWithFilter}} can fail with 
> java.lang.UnsupportedOperationException.
> Reproducible command
> {code:java}
> ./gradlew test --tests TestKnnVectorQuery.testRandomWithFilter 
> -Dtests.seed=1DA39B92702DAC45 -Dtests.multiplier=3
> {code}
> {code:java}
> org.apache.lucene.search.TestKnnVectorQuery > testRandomWithFilter FAILED
> java.lang.UnsupportedOperationException: exact search is not supported
> at 
> __randomizedtesting.SeedInfo.seed([1DA39B92702DAC45:6BEAC2197AD96AE0]:0)
> at 
> org.apache.lucene.search.TestKnnVectorQuery$ThrowingKnnVectorQuery.exactSearch(TestKnnVectorQuery.java:715)
> at 
> org.apache.lucene.search.KnnVectorQuery.searchLeaf(KnnVectorQuery.java:151)
> at 
> org.apache.lucene.search.KnnVectorQuery.rewrite(KnnVectorQuery.java:108)
> at 
> org.apache.lucene.search.ConstantScoreQuery.rewrite(ConstantScoreQuery.java:44)
> at 
> org.apache.lucene.search.IndexSearcher.rewrite(IndexSearcher.java:789)
> at 
> org.apache.lucene.tests.search.AssertingIndexSearcher.rewrite(AssertingIndexSearcher.java:69)
> at 
> org.apache.lucene.search.IndexSearcher.rewrite(IndexSearcher.java:803)
> at 
> org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:685)
> at 
> org.apache.lucene.search.IndexSearcher.searchAfter(IndexSearcher.java:667)
> at 
> org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:584)
> at 
> org.apache.lucene.search.TestKnnVectorQuery.testRandomWithFilter(TestKnnVectorQuery.java:556)
> {code}
> In some edge cases (depending on the random seed), 
> [KnnVectorQuery.java#147|https://github.com/apache/lucene/blob/fe9d26178d033f585c08a5e86708063ac0ec0c9e/lucene/core/src/java/org/apache/lucene/search/KnnVectorQuery.java#L147]
>  becomes false, and then `exactSearch()` is called.
> The upper bound of [the test range query 
> (filter)|https://github.com/apache/lucene/blob/fe9d26178d033f585c08a5e86708063ac0ec0c9e/lucene/core/src/test/org/apache/lucene/search/TestKnnVectorQuery.java#L554]
>  could be 200 (the max value of "tag" field + 1) instead of lower + 150 to 
> make it "unrestrictive"?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

[ANNOUNCE] Apache Lucene 9.3.0 released

2022-07-29 Thread Ignacio Vera

29 July 2022 - Apache Lucene™ 9.3.0 available

The Lucene PMC is pleased to announce the release of Apache Lucene 9.3.0.

Apache Lucene is a high-performance, full-featured search engine library
written entirely in Java. It is a technology suitable for nearly any
application that requires structured search, full-text search, faceting,
nearest-neighbor search across high-dimensionality vectors, spell
correction or query suggestions.

This release contains numerous bug fixes, optimizations, and improvements,
some of which are highlighted below. The release is available for immediate
download at:
https://lucene.apache.org/core/downloads.html

Lucene 9.3.0 Release Highlights:
• Merge on full flush is enabled now by default with a timeout of
500ms.
• Add getAllChildren functionality to facets.
• Added facetsets module for high dimensional (hyper-rectangle)
faceting.
• Top-level two-clause disjunctions sorted by score now use the
block-max MAXSCORE algorithm.
• When running KnnVectorQuery with a filter, reuse the cached
filter bit set.

Please read CHANGES.txt for a full list of new features and changes:

https://lucene.apache.org/core/9_3_0/changes/Changes.html

Note: The Apache Software Foundation uses an extensive mirroring network for
distributing releases. It is possible that the mirror you are using may not
have
replicated the release yet. If that is the case, please try another mirror.
This also applies to Maven access.

[ANNOUNCE] Apache Lucene 9.3.0 released

2022-07-29 Thread Ignacio Vera

29 July 2022 - Apache Lucene™ 9.3.0 available

The Lucene PMC is pleased to announce the release of Apache Lucene 9.3.0.

Apache Lucene is a high-performance, full-featured search engine library
written entirely in Java. It is a technology suitable for nearly any
application that requires structured search, full-text search, faceting,
nearest-neighbor search across high-dimensionality vectors, spell
correction or query suggestions.

This release contains numerous bug fixes, optimizations, and improvements,
some of which are highlighted below. The release is available for immediate
download at:
https://lucene.apache.org/core/downloads.html

Lucene 9.3.0 Release Highlights:
• Merge on full flush is enabled now by default with a timeout of
500ms.
• Add getAllChildren functionality to facets.
• Added facetsets module for high dimensional (hyper-rectangle)
faceting.
• Top-level two-clause disjunctions sorted by score now use the
block-max MAXSCORE algorithm.
• When running KnnVectorQuery with a filter, reuse the cached
filter bit set.

Please read CHANGES.txt for a full list of new features and changes:

https://lucene.apache.org/core/9_3_0/changes/Changes.html

Note: The Apache Software Foundation uses an extensive mirroring network for
distributing releases. It is possible that the mirror you are using may not
have
replicated the release yet. If that is the case, please try another mirror.
This also applies to Maven access.

Re: [VOTE] Release Lucene 9.3.0 RC1

2022-07-28 Thread Ignacio Vera

Hi Uwe,

Yes, I closed the vote already and I followed the instructions in the
release manager. One of the instructions is to delete the artifacts from
the staging area so I'm not sure why those are still there.
I have already pushed the artifacts to maven for publishing. I am very
sorry that Policeman Jenkins did not have the time to run.

Cheers,

Ignacio


On Thu, Jul 28, 2022 at 5:56 PM Uwe Schindler  wrote:

> It was late, but the folders of previous releases are still there, the
> last one disappeared from servers, while previous ones are still here:
>
> https://dist.apache.org/repos/dist/dev/lucene/
> <https://dist.apache.org/repos/dist/dev/lucene/lucene-9.3.0-RC1-rev-d25cebcef7a80369f4dfb9285ca7360a810b75dc>
>
>
> Uwe
>
>
> Am 28.07.2022 um 17:42 schrieb Uwe Schindler:
>
> Was the vote already over, because Policeman Jenkins failed to check?
>
> https://jenkins.thetaphi.de/job/Lucene-Release-Tester/18/console
> Am 25.07.2022 um 13:12 schrieb Ignacio Vera:
>
> Please vote for release candidate 1 for Lucene 9.3.0
>
>
> The artifacts can be downloaded from:
>
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.3.0-RC1-rev-d25cebcef7a80369f4dfb9285ca7360a810b75dc
>
>
> You can run the smoke tester directly with this command:
>
>
> python3 -u dev-tools/scripts/smokeTestRelease.py \
>
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.3.0-RC1-rev-d25cebcef7a80369f4dfb9285ca7360a810b75dc
>
>
> The vote will be open for at least 72 hours i.e. until 2022-07-28 12:00
> UTC.
>
>
> [ ] +1  approve
>
> [ ] +0  no opinion
>
> [ ] -1  disapprove (and reason why)
>
>
> Here is my +1
>
> --
> Uwe Schindler
> Achterdiek 19, D-28357 Bremenhttps://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> --
> Uwe Schindler
> Achterdiek 19, D-28357 Bremenhttps://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>

[RESULT] [VOTE] Release Lucene 9.3.0 RC1

2022-07-28 Thread Ignacio Vera

It's been >72h since the vote was initiated and the result is:


+1  7  (6 binding)

 0  0

-1  0


This vote has PASSED

Re: Welcome Vigya Sharma as Lucene committer

2022-07-28 Thread Ignacio Vera

Congratulations and welcome Vigya!

On Thu, Jul 28, 2022 at 9:34 AM Adrien Grand  wrote:

> I'm pleased to announce that Vigya Sharma has accepted the PMC's
> invitation to become a committer.
>
> Vigya, the tradition is that new committers introduce themselves with a
> brief bio.
>
> Congratulations and welcome!
>
> --
> Adrien
>

Re: New branch and feature freeze for Lucene 9.3.0

2022-07-27 Thread Ignacio Vera

Thanks Adrien! It sounds much more exciting indeed.

On Tue, Jul 26, 2022 at 6:35 PM Adrien Grand  wrote:

> Thanks Ignacio! I tried to iterate on some release highlights to make them
> sound more exciting.
>
> On Mon, Jul 25, 2022 at 5:05 PM Ignacio Vera  wrote:
>
>> Ignacio Vera 
>> Jul 20, 2022, 1:41 PM (5 days ago)
>> to dev
>> Adrien told me that I sent the wrong link, I thought I could share the
>> draft before publishing.
>> Here  the draft for the release highlights. I have probably missed things
>> that should be included so please feel free to add them.
>>
>> https://cwiki.apache.org/confluence/display/LUCENE/Release+Notes+9.3
>>
>>
>> On Sat, Jul 23, 2022 at 9:22 AM Ignacio Vera  wrote:
>>
>>> No worries Greg, I approved the change so feel free to push it whenever
>>> you have time.
>>>
>>> Cheers,
>>>
>>> Ignacio
>>>
>>> On Sat, Jul 23, 2022 at 1:22 AM Greg Miller  wrote:
>>>
>>>> OK, as frustrating as this is, it looks like there was still another
>>>> bug in this same test uncovered last night. I have another PR open to
>>>> patch this into 9.3 here: https://github.com/apache/lucene/pull/1044
>>>>
>>>> I also reopened https://issues.apache.org/jira/browse/LUCENE-10659 as
>>>> a proposed 9.3 block to pick up this fix. If the test remains
>>>> problematic after this patch, I'll just revert it out of 9.3 until it
>>>> proves more stable. Apologies.
>>>>
>>>> Cheers,
>>>> -Greg
>>>>
>>>> On Thu, Jul 21, 2022 at 7:59 AM Greg Miller  wrote:
>>>> >
>>>> > Ack, thanks Ignacio for the quick approval. Just merged the fix onto
>>>> > the 9.3 branch.
>>>> >
>>>> > Cheers,
>>>> > -Greg
>>>> >
>>>> > On Thu, Jul 21, 2022 at 12:32 AM Ignacio Vera 
>>>> wrote:
>>>> > >
>>>> > > Hi Greg,
>>>> > >
>>>> > > Yes please fix the test in branch 9.3, I have approved the PR.
>>>> > >
>>>> > > On Thu, Jul 21, 2022 at 12:08 AM Greg Miller 
>>>> wrote:
>>>> > >>
>>>> > >> Thanks Ignacio! I just created
>>>> > >> https://issues.apache.org/jira/browse/LUCENE-10659 as a proposed
>>>> > >> blocker for 9.3. It's a small bug fix for a unit test I recently
>>>> > >> introduced on the 9x branch (one of the last things to get pulled
>>>> into
>>>> > >> the 9.3 candidate). I think we ought to fix this test before
>>>> cutting a
>>>> > >> 9.3 release. There's a PR associated with the issue already (the
>>>> > >> change is already patched into main/branch_9x).
>>>> > >>
>>>> > >> Cheers,
>>>> > >> -Greg
>>>> > >>
>>>> > >> On Wed, Jul 20, 2022 at 4:42 AM Ignacio Vera 
>>>> wrote:
>>>> > >> >
>>>> > >> > Please find here the draft for the release highlights. I have
>>>> probably missed things that should be included so please feel free to add
>>>> them.
>>>> > >> >
>>>> > >> >
>>>> https://cwiki.apache.org/confluence/pages/resumedraft.action?draftId=217391905
>>>> > >> >
>>>> > >> > On Wed, Jul 20, 2022 at 10:17 AM Ignacio Vera 
>>>> wrote:
>>>> > >> >>
>>>> > >> >> NOTICE:
>>>> > >> >>
>>>> > >> >>
>>>> > >> >> Branch branch_9_3 has been cut and versions updated to 9.4 on
>>>> stable branch.
>>>> > >> >>
>>>> > >> >>
>>>> > >> >> Please observe the normal rules:
>>>> > >> >>
>>>> > >> >>
>>>> > >> >> * No new features may be committed to the branch.
>>>> > >> >>
>>>> > >> >> * Documentation patches, build patches and serious bug fixes
>>>> may be
>>>> > >> >>
>>>> > >> >>   committed to the branch. However, you should submit all
&g

Re: New branch and feature freeze for Lucene 9.3.0

2022-07-25 Thread Ignacio Vera

Ignacio Vera 
Jul 20, 2022, 1:41 PM (5 days ago)
to dev
Adrien told me that I sent the wrong link, I thought I could share the
draft before publishing.
Here  the draft for the release highlights. I have probably missed things
that should be included so please feel free to add them.

https://cwiki.apache.org/confluence/display/LUCENE/Release+Notes+9.3


On Sat, Jul 23, 2022 at 9:22 AM Ignacio Vera  wrote:

> No worries Greg, I approved the change so feel free to push it whenever
> you have time.
>
> Cheers,
>
> Ignacio
>
> On Sat, Jul 23, 2022 at 1:22 AM Greg Miller  wrote:
>
>> OK, as frustrating as this is, it looks like there was still another
>> bug in this same test uncovered last night. I have another PR open to
>> patch this into 9.3 here: https://github.com/apache/lucene/pull/1044
>>
>> I also reopened https://issues.apache.org/jira/browse/LUCENE-10659 as
>> a proposed 9.3 block to pick up this fix. If the test remains
>> problematic after this patch, I'll just revert it out of 9.3 until it
>> proves more stable. Apologies.
>>
>> Cheers,
>> -Greg
>>
>> On Thu, Jul 21, 2022 at 7:59 AM Greg Miller  wrote:
>> >
>> > Ack, thanks Ignacio for the quick approval. Just merged the fix onto
>> > the 9.3 branch.
>> >
>> > Cheers,
>> > -Greg
>> >
>> > On Thu, Jul 21, 2022 at 12:32 AM Ignacio Vera 
>> wrote:
>> > >
>> > > Hi Greg,
>> > >
>> > > Yes please fix the test in branch 9.3, I have approved the PR.
>> > >
>> > > On Thu, Jul 21, 2022 at 12:08 AM Greg Miller 
>> wrote:
>> > >>
>> > >> Thanks Ignacio! I just created
>> > >> https://issues.apache.org/jira/browse/LUCENE-10659 as a proposed
>> > >> blocker for 9.3. It's a small bug fix for a unit test I recently
>> > >> introduced on the 9x branch (one of the last things to get pulled
>> into
>> > >> the 9.3 candidate). I think we ought to fix this test before cutting
>> a
>> > >> 9.3 release. There's a PR associated with the issue already (the
>> > >> change is already patched into main/branch_9x).
>> > >>
>> > >> Cheers,
>> > >> -Greg
>> > >>
>> > >> On Wed, Jul 20, 2022 at 4:42 AM Ignacio Vera 
>> wrote:
>> > >> >
>> > >> > Please find here the draft for the release highlights. I have
>> probably missed things that should be included so please feel free to add
>> them.
>> > >> >
>> > >> >
>> https://cwiki.apache.org/confluence/pages/resumedraft.action?draftId=217391905
>> > >> >
>> > >> > On Wed, Jul 20, 2022 at 10:17 AM Ignacio Vera 
>> wrote:
>> > >> >>
>> > >> >> NOTICE:
>> > >> >>
>> > >> >>
>> > >> >> Branch branch_9_3 has been cut and versions updated to 9.4 on
>> stable branch.
>> > >> >>
>> > >> >>
>> > >> >> Please observe the normal rules:
>> > >> >>
>> > >> >>
>> > >> >> * No new features may be committed to the branch.
>> > >> >>
>> > >> >> * Documentation patches, build patches and serious bug fixes may
>> be
>> > >> >>
>> > >> >>   committed to the branch. However, you should submit all patches
>> you
>> > >> >>
>> > >> >>   want to commit to Jira first to give others the chance to review
>> > >> >>
>> > >> >>   and possibly vote against the patch. Keep in mind that it is our
>> > >> >>
>> > >> >>   main intention to keep the branch as stable as possible.
>> > >> >>
>> > >> >> * All patches that are intended for the branch should first be
>> committed
>> > >> >>
>> > >> >>   to the unstable branch, merged into the stable branch, and then
>> into
>> > >> >>
>> > >> >>   the current release branch.
>> > >> >>
>> > >> >> * Normal unstable and stable branch development may continue as
>> usual.
>> > >> >>
>> > >> >>   However, if you plan to commit a big change to the unstable
>> branch
>> > >> >>
>> > >> >>   while the branch feature freeze is in effect, think twice:
>> can't the
>> > >> >>
>> > >> >>   addition wait a couple more days? Merges of bug fixes into the
>> branch
>> > >> >>
>> > >> >>   may become more difficult.
>> > >> >>
>> > >> >> * Only Jira issues with Fix version 9.3 and priority "Blocker"
>> will delay
>> > >> >>
>> > >> >>   a release candidate build.
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >> The only step missing is to add the Jenkins job on the release
>> branch which is something I don't really know how to do it, hopefully
>> someone can help here.
>> > >> >>
>> > >> >>
>> > >> >> I am planning to build the first RC next Monday if there are no
>> issues.
>> > >>
>> > >> -
>> > >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> > >> For additional commands, e-mail: dev-h...@lucene.apache.org
>> > >>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>>

[VOTE] Release Lucene 9.3.0 RC1

2022-07-25 Thread Ignacio Vera

Please vote for release candidate 1 for Lucene 9.3.0


The artifacts can be downloaded from:

https://dist.apache.org/repos/dist/dev/lucene/lucene-9.3.0-RC1-rev-d25cebcef7a80369f4dfb9285ca7360a810b75dc


You can run the smoke tester directly with this command:


python3 -u dev-tools/scripts/smokeTestRelease.py \

https://dist.apache.org/repos/dist/dev/lucene/lucene-9.3.0-RC1-rev-d25cebcef7a80369f4dfb9285ca7360a810b75dc


The vote will be open for at least 72 hours i.e. until 2022-07-28 12:00 UTC.


[ ] +1  approve

[ ] +0  no opinion

[ ] -1  disapprove (and reason why)


Here is my +1

Re: New branch and feature freeze for Lucene 9.3.0

2022-07-23 Thread Ignacio Vera

No worries Greg, I approved the change so feel free to push it whenever you
have time.

Cheers,

Ignacio

On Sat, Jul 23, 2022 at 1:22 AM Greg Miller  wrote:

> OK, as frustrating as this is, it looks like there was still another
> bug in this same test uncovered last night. I have another PR open to
> patch this into 9.3 here: https://github.com/apache/lucene/pull/1044
>
> I also reopened https://issues.apache.org/jira/browse/LUCENE-10659 as
> a proposed 9.3 block to pick up this fix. If the test remains
> problematic after this patch, I'll just revert it out of 9.3 until it
> proves more stable. Apologies.
>
> Cheers,
> -Greg
>
> On Thu, Jul 21, 2022 at 7:59 AM Greg Miller  wrote:
> >
> > Ack, thanks Ignacio for the quick approval. Just merged the fix onto
> > the 9.3 branch.
> >
> > Cheers,
> > -Greg
> >
> > On Thu, Jul 21, 2022 at 12:32 AM Ignacio Vera  wrote:
> > >
> > > Hi Greg,
> > >
> > > Yes please fix the test in branch 9.3, I have approved the PR.
> > >
> > > On Thu, Jul 21, 2022 at 12:08 AM Greg Miller 
> wrote:
> > >>
> > >> Thanks Ignacio! I just created
> > >> https://issues.apache.org/jira/browse/LUCENE-10659 as a proposed
> > >> blocker for 9.3. It's a small bug fix for a unit test I recently
> > >> introduced on the 9x branch (one of the last things to get pulled into
> > >> the 9.3 candidate). I think we ought to fix this test before cutting a
> > >> 9.3 release. There's a PR associated with the issue already (the
> > >> change is already patched into main/branch_9x).
> > >>
> > >> Cheers,
> > >> -Greg
> > >>
> > >> On Wed, Jul 20, 2022 at 4:42 AM Ignacio Vera 
> wrote:
> > >> >
> > >> > Please find here the draft for the release highlights. I have
> probably missed things that should be included so please feel free to add
> them.
> > >> >
> > >> >
> https://cwiki.apache.org/confluence/pages/resumedraft.action?draftId=217391905
> > >> >
> > >> > On Wed, Jul 20, 2022 at 10:17 AM Ignacio Vera 
> wrote:
> > >> >>
> > >> >> NOTICE:
> > >> >>
> > >> >>
> > >> >> Branch branch_9_3 has been cut and versions updated to 9.4 on
> stable branch.
> > >> >>
> > >> >>
> > >> >> Please observe the normal rules:
> > >> >>
> > >> >>
> > >> >> * No new features may be committed to the branch.
> > >> >>
> > >> >> * Documentation patches, build patches and serious bug fixes may be
> > >> >>
> > >> >>   committed to the branch. However, you should submit all patches
> you
> > >> >>
> > >> >>   want to commit to Jira first to give others the chance to review
> > >> >>
> > >> >>   and possibly vote against the patch. Keep in mind that it is our
> > >> >>
> > >> >>   main intention to keep the branch as stable as possible.
> > >> >>
> > >> >> * All patches that are intended for the branch should first be
> committed
> > >> >>
> > >> >>   to the unstable branch, merged into the stable branch, and then
> into
> > >> >>
> > >> >>   the current release branch.
> > >> >>
> > >> >> * Normal unstable and stable branch development may continue as
> usual.
> > >> >>
> > >> >>   However, if you plan to commit a big change to the unstable
> branch
> > >> >>
> > >> >>   while the branch feature freeze is in effect, think twice: can't
> the
> > >> >>
> > >> >>   addition wait a couple more days? Merges of bug fixes into the
> branch
> > >> >>
> > >> >>   may become more difficult.
> > >> >>
> > >> >> * Only Jira issues with Fix version 9.3 and priority "Blocker"
> will delay
> > >> >>
> > >> >>   a release candidate build.
> > >> >>
> > >> >>
> > >> >>
> > >> >> The only step missing is to add the Jenkins job on the release
> branch which is something I don't really know how to do it, hopefully
> someone can help here.
> > >> >>
> > >> >>
> > >> >> I am planning to build the first RC next Monday if there are no
> issues.
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > >> For additional commands, e-mail: dev-h...@lucene.apache.org
> > >>
>
> -
> 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

2022-07-21 Thread Ignacio Vera

indeed, just waiting for him to do the honours and push the PR.

On Thu, Jul 21, 2022 at 12:30 PM Michael McCandless <
luc...@mikemccandless.com> wrote:

> Greg fixed a test failure that impacts 9.3, and opened a PR and blocker
> issue: https://issues.apache.org/jira/browse/LUCENE-10659
>
> I think we should merge it for 9.3.0?
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Wed, Jul 20, 2022 at 7:43 PM Julie Tibshirani 
> wrote:
>
>> Hello Mayya, I can share my view. Strictly speaking, we only need a new
>> codec version if the on-disk format changes for some type (like kNN vectors
>> in this case). Otherwise we can just evolve the logic in the same way we do
>> with other code, making the improvements in-place. Alessandro's PR is a
>> good example of this -- it's a refactor that happens to touch the
>> vectors reader code. It doesn't require a totally new codec version.
>>
>> With your PR for LUCENE-10592, I don't think we technically need a new
>> codec for it, because the on-disk format remains the same. But since it's
>> such a big change that deeply affects the vectors writing logic, it feels
>> convenient that we're making it in a new format (maybe feels a bit clearer/
>> safer).
>>
>> Julie
>>
>> On Wed, Jul 20, 2022 at 4:21 PM Mayya Sharipova
>>  wrote:
>>
>>> Hi Julie,
>>> thanks for raising this point, I was also thinking about it.
>>> I think it would be valuable to clarify what constitutes the format
>>> changes. Is on disk changes a necessary requirement for it? Or is it enough
>>> that codec readers and writers change their behaviour?
>>>
>>> For example, for LUCENE-10592, there are extensive changes about how
>>> codec readers and writers behave, while the format on disk stays the same.
>>> Specifically for the release 9.3, Alessandro also introduced some
>>> changes  <https://github.com/apache/lucene/pull/926>to codec readers
>>> while the format on disk stayed the same.
>>>
>>>
>>>
>>>
>>> On Wed, Jul 20, 2022 at 4:22 PM Julie Tibshirani 
>>> wrote:
>>>
>>>> Hello everyone,
>>>>
>>>> We had preemptively created a Lucene93Codec to support the vector
>>>> search changes (Mike's work in LUCENE-10577, Mayya's work in LUCENE-10592).
>>>> However neither of these changes made it for 9.3, so there have not been
>>>> any real format changes-- Lucene93Codec is the same as Lucene92Codec.
>>>> Should we remove Lucene93Codec on branch_9_3 (effectively reverting
>>>> https://github.com/apache/lucene/pull/924) ?
>>>>
>>>> Julie
>>>>
>>>> On Tue, Jul 19, 2022 at 11:02 AM Mayya Sharipova
>>>>  wrote:
>>>>
>>>>> Thanks Adrien, it is indeed a big change, also would be nice to see
>>>>> benchmarks after it is merged.
>>>>>
>>>>> So, Ignacio, please don't wait for LUCENE-10592, we will not be able
>>>>> to make it for tomorrow.
>>>>>
>>>>> On Tue, Jul 19, 2022 at 10:38 AM Adrien Grand 
>>>>> wrote:
>>>>>
>>>>>> While I can understand the excitement about LUCENE-10592, it's also a
>>>>>> big change, maybe we should not even try to get it in before cutting the
>>>>>> branch?
>>>>>>
>>>>>> On Tue, Jul 19, 2022 at 4:09 PM Mayya Sharipova
>>>>>>  wrote:
>>>>>>
>>>>>>> Thanks for the reminder about the release, Ignacio!
>>>>>>> About LUCENE-10592
>>>>>>> <https://issues.apache.org/jira/browse/LUCENE-10592>  I will see
>>>>>>> what progress we can make today, and will let you know before Wednesday 
>>>>>>> at
>>>>>>> 9:00 CEST.
>>>>>>>
>>>>>>> On Tue, Jul 19, 2022 at 7:12 AM Michael Sokolov 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Thanks for checking, but please don't wait for LUCENE-10577. It's
>>>>>>>> not clear when that might get resolved
>>>>>>>>
>>>>>>>> On Mon, Jul 18, 2022, 10:42 AM Ignacio Vera 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Just a quick reminder I plan to cut the 9.3 branch this Wednesday
>>>>>>>>> at 9:00 CEST. Let me know if there is any issue.

Re: New branch and feature freeze for Lucene 9.3.0

2022-07-21 Thread Ignacio Vera

Hi Greg,

Yes please fix the test in branch 9.3, I have approved the PR.

On Thu, Jul 21, 2022 at 12:08 AM Greg Miller  wrote:

> Thanks Ignacio! I just created
> https://issues.apache.org/jira/browse/LUCENE-10659 as a proposed
> blocker for 9.3. It's a small bug fix for a unit test I recently
> introduced on the 9x branch (one of the last things to get pulled into
> the 9.3 candidate). I think we ought to fix this test before cutting a
> 9.3 release. There's a PR associated with the issue already (the
> change is already patched into main/branch_9x).
>
> Cheers,
> -Greg
>
> On Wed, Jul 20, 2022 at 4:42 AM Ignacio Vera  wrote:
> >
> > Please find here the draft for the release highlights. I have probably
> missed things that should be included so please feel free to add them.
> >
> >
> https://cwiki.apache.org/confluence/pages/resumedraft.action?draftId=217391905
> >
> > On Wed, Jul 20, 2022 at 10:17 AM Ignacio Vera  wrote:
> >>
> >> NOTICE:
> >>
> >>
> >> Branch branch_9_3 has been cut and versions updated to 9.4 on stable
> branch.
> >>
> >>
> >> Please observe the normal rules:
> >>
> >>
> >> * No new features may be committed to the branch.
> >>
> >> * Documentation patches, build patches and serious bug fixes may be
> >>
> >>   committed to the branch. However, you should submit all patches you
> >>
> >>   want to commit to Jira first to give others the chance to review
> >>
> >>   and possibly vote against the patch. Keep in mind that it is our
> >>
> >>   main intention to keep the branch as stable as possible.
> >>
> >> * All patches that are intended for the branch should first be committed
> >>
> >>   to the unstable branch, merged into the stable branch, and then into
> >>
> >>   the current release branch.
> >>
> >> * Normal unstable and stable branch development may continue as usual.
> >>
> >>   However, if you plan to commit a big change to the unstable branch
> >>
> >>   while the branch feature freeze is in effect, think twice: can't the
> >>
> >>   addition wait a couple more days? Merges of bug fixes into the branch
> >>
> >>   may become more difficult.
> >>
> >> * Only Jira issues with Fix version 9.3 and priority "Blocker" will
> delay
> >>
> >>   a release candidate build.
> >>
> >>
> >>
> >> The only step missing is to add the Jenkins job on the release branch
> which is something I don't really know how to do it, hopefully someone can
> help here.
> >>
> >>
> >> I am planning to build the first RC next Monday if there are no issues.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: New branch and feature freeze for Lucene 9.3.0

2022-07-20 Thread Ignacio Vera

Please find here the draft for the release highlights. I have probably
missed things that should be included so please feel free to add them.

https://cwiki.apache.org/confluence/pages/resumedraft.action?draftId=217391905

On Wed, Jul 20, 2022 at 10:17 AM Ignacio Vera  wrote:

> NOTICE:
>
>
> Branch branch_9_3 has been cut and versions updated to 9.4 on stable
> branch.
>
>
> Please observe the normal rules:
>
>
> * No new features may be committed to the branch.
>
> * Documentation patches, build patches and serious bug fixes may be
>
>   committed to the branch. However, you should submit all patches you
>
>   want to commit to Jira first to give others the chance to review
>
>   and possibly vote against the patch. Keep in mind that it is our
>
>   main intention to keep the branch as stable as possible.
>
> * All patches that are intended for the branch should first be committed
>
>   to the unstable branch, merged into the stable branch, and then into
>
>   the current release branch.
>
> * Normal unstable and stable branch development may continue as usual.
>
>   However, if you plan to commit a big change to the unstable branch
>
>   while the branch feature freeze is in effect, think twice: can't the
>
>   addition wait a couple more days? Merges of bug fixes into the branch
>
>   may become more difficult.
>
> * Only Jira issues with Fix version 9.3 and priority "Blocker" will delay
>
>   a release candidate build.
>
>
>
> The only step missing is to add the Jenkins job on the release branch
> which is something I don't really know how to do it, hopefully someone can
> help here.
>
>
> I am planning to build the first RC next Monday if there are no issues.
>

New branch and feature freeze for Lucene 9.3.0

2022-07-20 Thread Ignacio Vera

NOTICE:


Branch branch_9_3 has been cut and versions updated to 9.4 on stable branch.


Please observe the normal rules:


* No new features may be committed to the branch.

* Documentation patches, build patches and serious bug fixes may be

  committed to the branch. However, you should submit all patches you

  want to commit to Jira first to give others the chance to review

  and possibly vote against the patch. Keep in mind that it is our

  main intention to keep the branch as stable as possible.

* All patches that are intended for the branch should first be committed

  to the unstable branch, merged into the stable branch, and then into

  the current release branch.

* Normal unstable and stable branch development may continue as usual.

  However, if you plan to commit a big change to the unstable branch

  while the branch feature freeze is in effect, think twice: can't the

  addition wait a couple more days? Merges of bug fixes into the branch

  may become more difficult.

* Only Jira issues with Fix version 9.3 and priority "Blocker" will delay

  a release candidate build.



The only step missing is to add the Jenkins job on the release branch which
is something I don't really know how to do it, hopefully someone can help
here.


I am planning to build the first RC next Monday if there are no issues.

Re: Lucene 9.3.0 release

2022-07-18 Thread Ignacio Vera

Just a quick reminder I plan to cut the 9.3 branch this Wednesday at 9:00
CEST. Let me know if there is any issue.

@Mike: I see that LUCENE-10577
<https://issues.apache.org/jira/browse/LUCENE-10577> is still under API
discussions, Do you think it will make it to the release? LUCENE-10592
<https://issues.apache.org/jira/browse/LUCENE-10592>  seems to have made
good progress, would you think it will be ready?
@Nick: I gave you feedback on the PR. I think it is way too risky to add an
encoding in a rush. I recommend adding the change in the sandbox if you
want to iterate in there or wait for another release where there is more
time to think through the encoding.

Cheers,

Ignacio

On Wed, Jul 13, 2022 at 2:09 AM Nicholas Knize  wrote:

> I'd like to get ShapeDocValuesField in for the 9.3 release (
> https://issues.apache.org/jira/browse/LUCENE-10654). It's a nice feature
> for enabling facets and aggregations over XYShape and LatLonShape field
> types and could make for a good 9.3 geo highlight.
>
> Nicholas Knize, Ph.D., GISP
> Principal Engineer - Search  |  Amazon
> Apache Lucene PMC Member and Committer
> nkn...@apache.org
>
>
> On Tue, Jul 12, 2022 at 2:50 PM Ignacio Vera  wrote:
>
>> Thanks for the heads up, I am planning to cut the brunch middle next
>> week, Wednesday July 20th.
>> Let me know at the beginning of next week if there is any issue from your
>> side.
>>
>> cheers,
>>
>> Ignacio
>>
>> On Mon, Jul 11, 2022 at 4:21 PM Michael Sokolov 
>> wrote:
>>
>>> 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: [ccp4bb] problems in Rfree-flags when refining with REFMAC and processing with STARANISO

2022-07-13 Thread Vera Pfanzagl

Dear Clemens, 

Thank you so much! This was in the end the solution =) A lot of combining mtz 
files back and forth=) 

But as always one last thing remains... 

You write that I should make sure REFMAC reads in the test-set from the 
staraniso.mtz and does not replace it with a new one.
This would only be the case if it generates a new test set when I initially 
import the reflection file, right? How can I check that retrospectively with my 
history-riddled file? 

cheers and thank you very much, Vrea

PS: the links in [2] are not accurate anymore, the interface of CCP4i2 export 
alone already looks completely different and does not seem to want external 
processing files.

>>> Clemens Vonrhein  07/12/22 2:50 PM >>>
Dear Vera,

On Tue, Jul 12, 2022 at 02:04:51PM +0200, Vera Pfanzagl wrote:
> >> What I initially did not know is that REFMAC and STARANISO do not go
> >> well together when it comes to the Rfree-flags in the diffraction
> >> cut-off regions.
> 
> >Just to clarify: REFMAC should have no problems with STARANISO
> >data. What you probably mean is that the unobservable reflections
> >outside of the cut-off surface - which might be considered via an
> >ellipsoidal aproximation - could be used for the DFc completion in
> >REFMAC?
> 
> 
> Yes this is what I meant, I just put it in very loose words =) but
> for future reference, this is a good step to take, right?

It might depend on how exactly you are running REFMAC (different
GUIs/interfaces might use different flags and defaults). According to

https://www2.mrc-lmb.cam.ac.uk/groups/murshudov/content/refmac/refmac_keywords.html#id.4d3ffe3d758a

it says

  When calculating map coefficients REFMAC by default tries to restore
  missing reflections. Statistical basis of this is that expected
  value of unknown structure factors for missing reflections are
  better approximated using DFc than with 0 values.

Which makes sense /if/ those missing reflections are expected to be
larger than 0. This would be true for observations missed due to a
cusp, overloads, detector module gaps etc.

However, in the reciprocal space regions where we don't expect any
observable intensity, these measurements are expected to be ~0 and
should therefore not filled-in with D*Fc values. Think of a perfect,
isotropically diffracting crystal where by any measure (CC1/2, I/sigI,
Rpim etc) we would say that the highest diffraction limit is 3A: we
would never compute map coefficients to 2A with everything in the 3-2A
range consisting of D*Fc values just because we could generate Miller
indices to any diffraction limit we chose ... right?

The same is true for an anisotropic dataset - just that instead of an
isotropic (sphere) cut-off surface (to e.g. 3A) we now have an
anisotropic (approximated e.g. by an ellipsoid) cut-off surface
(described by three numbers if approximated by an ellipsoid). We
shouldn't compute/restore map coefficients in the reciprocal space
regions where we don't expect any observable intensity at all.

Of course, if the model is perfect, those Fc (Fcalc) values would be
very close to zero anyway and the D attenuation factor also plays a
role ... but since no model is perfect that can't always be
guaranteed.

> I will hopefully have a few more crystals with the same issue and I
> would also now stick to this file.

BUSTER understands the SA_flag generated by STARANISO, which defines
those reflections that should get a D*Fc value (if no observation
present) in sync with the anisotropic model it used. It will create
three sets of 2mFo-DFc maps: only observations, filled-in within the
anisotropic model and filled-in within the full diffraction limit
sphere.

REFMAC needs to be slightly fooled via the procedure described at [1]
- and hopefully, the interface you use for driving REFMAC is not
trying to be clever and generates again a complete set of test-set
flags to the diffraction limit of the MTZ file. So make sure REFMAC
sees the MTZ file exactly as prepared in [1].

> >Take the Data_1_autoPROC_STARANISO_all.cif and combine it [1] with the
> >mmCIF from your refinement step: ensure that the data block with the
> >reflection data that went /into/ your refinement is given as the first
> >block. By convention, this is what e.g. PDB deposition/validation
> >software will use for re-computing various statistics.
> 
> >I would be inclined to go back to your original REFMAC refinement
> >(before you did all that SFTOOLS, Phenix-again, server, conversion
> >steps): do you have just an output MTZ file and no reflection mmCIF?
> >Maybe by re-running the same job you could switch on some option to
> >trigger writing of the reflection data in mmCIF format? Maybe even
> >switching off the DFc completion and/or re-scaling?
> 
> 
> PHENIX has this option to export the data as an mmcif but I canno

Re: Lucene 9.3.0 release

2022-07-12 Thread Ignacio Vera

Thanks for the heads up, I am planning to cut the brunch middle next week,
Wednesday July 20th.
Let me know at the beginning of next week if there is any issue from your
side.

cheers,

Ignacio

On Mon, Jul 11, 2022 at 4:21 PM Michael Sokolov  wrote:

> 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
>
>

[jira] [Commented] (LUCENE-10628) Enable MatchingFacetSetCounts to use space partitioning data structures

2022-07-12 Thread Ignacio Vera (Jira)



[ 
https://issues.apache.org/jira/browse/LUCENE-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565882#comment-17565882
 ] 

Ignacio Vera commented on LUCENE-10628:
---

I have mainly worked with two type of trees in Lucene. 

* 
[KD-tree|https://github.com/apache/lucene/blob/35ca2d79f73c6dfaf5e648fe241f7e0b37084a90/lucene/core/src/java/org/apache/lucene/util/bkd/BKDWriter.java#L79]:
  It is complex to build so probably not suitable for building them on the fly 
but best structure for an index.

* [Interval 
tree|https://github.com/apache/lucene/blob/2d6ad2fee6dfd96388594f4de9b37c037efe8017/lucene/core/src/java/org/apache/lucene/geo/ComponentTree.java#L28]
 (I think originally introduced by Robert Muir):  Not as efficient as a kd-tree 
but much cheaper to build and suitable for small data.

>From a quick look I think you would be looking for an interval tree but mind 
>you that I have only worked with that tree for very low dimension. I guess 
>this kind of tree will quickly degenerate due to the [curse of 
>dimensionality|https://en.wikipedia.org/wiki/Curse_of_dimensionality]. How may 
>dimensions are you expecting to support?



> Enable MatchingFacetSetCounts to use space partitioning data structures
> ---
>
> Key: LUCENE-10628
> URL: https://issues.apache.org/jira/browse/LUCENE-10628
> Project: Lucene - Core
>  Issue Type: Improvement
>Reporter: Marc D'Mello
>Priority: Minor
>
> Currently, {{MatchingFacetSetCounts}} iterates over {{FacetSetMatcher}} 
> instances passed into it linearly. While this is fine in some cases, if we 
> have a large amount of {{FacetSetMatcher}}'s, this can be inefficient. We 
> should provide the option to users to enable the use of space partitioning 
> data structures (namely R trees and KD trees) so we can potentially scan over 
> these {{FacetSetMatcher}}'s in sub-linear time.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Re: [ccp4bb] problems in Rfree-flags when refining with REFMAC and processing with STARANISO

2022-07-12 Thread Vera Pfanzagl

Hi Clemens, 

Thank you for your help. 

Unfortunately, although I definitely learned a few things I have additional 
questions...

>> What I initially did not know is that REFMAC and STARANISO do not go
>> well together when it comes to the Rfree-flags in the diffraction
>> cut-off regions.

>Just to clarify: REFMAC should have no problems with STARANISO
>data. What you probably mean is that the unobservable reflections
>outside of the cut-off surface - which might be considered via an
>ellipsoidal aproximation - could be used for the DFc completion in
>REFMAC?

Yes this is what I meant, I just put it in very loose words =) but for future 
reference, this is a good step to take, right? I will hopefully have a few more 
crystals with the same issue and I would also now stick to this file. 

>Take the Data_1_autoPROC_STARANISO_all.cif and combine it [1] with the
>mmCIF from your refinement step: ensure that the data block with the
>reflection data that went /into/ your refinement is given as the first
>block. By convention, this is what e.g. PDB deposition/validation
>software will use for re-computing various statistics.

>I would be inclined to go back to your original REFMAC refinement
>(before you did all that SFTOOLS, Phenix-again, server, conversion
>steps): do you have just an output MTZ file and no reflection mmCIF?
>Maybe by re-running the same job you could switch on some option to
>trigger writing of the reflection data in mmCIF format? Maybe even
>switching off the DFc completion and/or re-scaling?

PHENIX  has this option to export the data as an mmcif but I cannot find this  
in CPP4i2 (which is where I use REFMAC). There is only the export and  
validation tool, but this is crashing because it expects processing data which 
is not there and which i cannot import either (I cannot select anything for 
Aimless XML) . And here is where my fluffy understanding of the mtz file format 
hits me over the head =) as long as an output is generated automatically there 
is the security that the right data is in the right place.

What I tried was to export the "old-style".mtz from CCP4i2 and then to convert 
it using the gemmi server. But gemmi requires intensities, which are missing in 
the REFMAC mtz, which contains these arrays: H K L FREER F SIGF FC PHIC FC_ALL 
PHIC_ALL FWT PHWT DELFWT PHDELWT FOM PHCOMB HLACOMB HLBCOMB HLCCOMB HLDCOMB 
FC_ALL_LS PHIC_ALL_LS. 

Could it be that a large part of my problem is deived from the mini-mtz output 
files that are generated by CPP4i2? 

I think this is where I am stuck, I do not know how to get the output mini-mtz 
together with the intensity data in one mtz file, or where to convert this mtz 
to a cif (and also not how to combine this with the cif file from autoproc, but 
this is a future problem)

cheers and thank you, Vera

and on a less pressing side... 

>> I then went to Phenix for molecular replacement and refined a few
>> rounds with Phenix.

>Ok.
a case of a go-to-the-well-known, as long as it works.

>> However one of my co-factors (a twice covalently linked heme) 
>> did not refine properly, which is why i switched the refinement to CCP4 
>> and used REFMAC.

>It might be interesting to find out what the differences in restraint
>dictionaries is here (this seems the most likely reason for such
>misbehaving ... and all refinement programs should handle heme
>residues correctly I guess).

Yes
 I think there is a problem with the heme restraints somewhere and I 
would be very grateful for any help in this regard, since I have more 
structures with a covalent heme linkage. COOT does not deal very well 
with the linkages and I had no way of generating the link record with 
AceDRG as it cannot yet deal with the heme iron. So I wrote a link 
dictionary for the two links (which i hope works). It seemed that both 
Buster and REFMAC can deal with the heme linkages, but PHENIX gradually 
shifts the "linked" atoms more and more apart with each refinement 
cycle, which is also what happens in COOT. 

>If you created a totally new test-set, you could indeed try and unbias
>the Rfree computations. On the other hand, since you have already
>validated your model parametrisation before (with the old test-set)
>there should not be any need to do everything from scratch again
>... however, since the resulting R/Rfree will not be decoupled you
>would have trouble reporting/depositing such a result as well ;-)

Yeah, i realize that now as well =) also this is exactly what happened.

cheers again

>>> Clemens Vonrhein  07/11/22 7:08 PM >>>
Hi Vera,

On Mon, Jul 11, 2022 at 04:51:32PM +0200, Vera Pfanzagl wrote:
> I am trying to get a structure with a bit of a history in terms of
> programs I have used into a deposit-able form.

Yeah ... real-life never follows th

Re: [ccp4bb] [EXTERNAL] [ccp4bb] problems in Rfree-flags when refining with REFMAC and processing with STARANISO

2022-07-11 Thread Vera Pfanzagl

Hello Joao, 


Thank you for your suggestion. Unfortunately i still seem to have a problem in 
the mtz file itself, from pdb-extract I get the following error message

data_info

_sf_convert.error
;
Warning: (data block=1): all status (80493) are assigned as 'x' (changed! 
'x'->'o')
Error: File () has no mandatory items 'F/I/F+/F-/I+/I-' (data block=1). 
;

_sf_convert.sf_information
;
Note: -wave is used for free data set.
Total number of data blocks = 1


Data_block_id=rsf,  pdbid=,  block_number=1


Number of reflections for validation set =80493
;


Which is again the same message I got from phenix and refmac. I don't get if 
this originates when going from autoproc to refmac or later? 

Cheers Vera





>>> "Carrapa Nunes Dias, Joao Miguel" 
>>> <8228c47b79c6-dmarc-requ...@jiscmail.ac.uk> 07/11/22 5:22 PM >>>
  Vera,
 I had a similar case and I solved it using the PDB tool pdb_extract from:
 https://pdb-extract.wwpdb.org/
 PDB Extract is a pre-deposition service for assembling structure files for 
wwPDB OneDep deposition .
  
 You have a pdb and you have a mtz file, then you should be able to convert 
them to the latest mmcif format.
  
 After that you can deposit your files in:
 https://deposit-1.wwpdb.org/deposition/
 https://validate-rcsb-2.wwpdb.org/
  
 Since you used anisotropic data and different software, the final R/Rfree will 
likely be different of the estimated during PDB validation, and you will have 
the opportunity to explain it to the person from the PDB that will help you 
during  your deposition.
  
 Finally, if you are using PHENIX, BUSTER, REFMAC/CCP4, you can also run a last 
refinement step with the latest version of the software.
 The latest version will ensure that the mmcif format is compatible with the 
PDB. Sometimes older versions of the software will give you that type of error.
  
 Good luck,
 Joao
  
  
   From: CCP4 bulletin board   On Behalf Of Vera Pfanzagl
 Sent: Monday, July 11, 2022 10:52 AM
 To: CCP4BB@JISCMAIL.AC.UK
 Subject: [EXTERNAL] [ccp4bb] problems in Rfree-flags when refining with REFMAC 
and processing with STARANISO
 
 
  
  Hello, 
 
   
 
  I am trying to get a structure with a bit of a history in terms of programs I 
have used into a deposit-able form. However  I have massif problems with the 
mtz labels, specifically  the Rfree flags and cannot figure out where my 
problem is derived from.
 
   
 
  Specifically I have collected diffraction data on a very anistropic crystal 
(3 A in one direction and 1.4 in the other) which I processed using AUTOPROC 
because I wanted  to make use of the inbuild STARANISO processing. I then went 
to Phenix for molecular replacement and refined a few rounds with Phenix. 
However one of my co-factors (a twice covalently linked heme) did not refine 
properly, which is why i switched the refinement  to CCP4 and used REFMAC. What 
I initially did not know is that REFMAC and STARANISO do not go well together 
when it comes to the Rfree-flags in the diffraction cut-off regions. 
 
   
 
  I went back and tried to use SFtools by CCP4 as described on  
https://staraniso.globalphasing.org/test_set_flags_about.html to generate a 
staraniso_mtz suitable for refinement in REFMAC, phased it again with my 
initial model and ran a refinement cycle, because I thought skipping a program 
might be a good idea. However  I do not know if the mtz file I get has the 
appropriate column labels and also I do not know how to convert it to an mmcif 
that includes the data from processing. i have never before tried to combine 
AUTOPROC-processed data with REFMAC data and am not very  familiar with REFMAC 
to begin with. I have tried the sftool server to validate the mtz from REFMAC 
processing but I get an error message 
 
  Converting SF file to mmcif format ... Warning: (data block=1): all status 
(80493) are assigned as 'x' (changed! 'x'->'o')Error: File () has no 
mandatory items 'F/I/F+/F-/I+/I-' (data block=1) 
   
 
  I tried to use Phenix (as it automatically converts the mtz to an mmcif file) 
by running a "mock"-refinement with fixed coordinates but the mmcif file I get 
out of this seems  to contain some wrongly labeled data fields in block 1 when 
I try to upload it to PDBs validation server. 
 
  Essentially it seems to contain some 3 data points in block 1 that have a 
? This is the error message I receive:
 
   
 
  Warning: (data block=1): 30301 reflections have status assigned as '?' 
(changed to 'x') Warning: (data block=1): 30301 reflections have wrong status. 
Not in list(o,f,x,-,<,h,l)  Warning: No wavelength value was found in SF file 
(data block=1).
 
   
 
  which is essentially the same as above, so I guess it is derived from the 
same problem.
 
   
 
  I would be very grateful for any help. 
 
   
 
 Cheers and thanks, Vera
  
   
 To unsubscribe from the CCP4BB list, click the following link:
 https://www.jiscmail.ac.

[ccp4bb] problems in Rfree-flags when refining with REFMAC and processing with STARANISO

2022-07-11 Thread Vera Pfanzagl

Hello, 


I am 
trying to get a structure with a bit of a history in terms of 
programs I have used into a deposit-able form. However  I have massif problems 
with the mtz labels, specifically the Rfree flags and 
cannot figure out where my problem is derived from.


Specifically
 I have collected diffraction data on a very anistropic crystal (3 A in 
one direction and 1.4 in the other) which I processed using AUTOPROC 
because I wanted to make use of the inbuild STARANISO processing. I then
 went to Phenix for molecular replacement and refined a few rounds with 
Phenix. However one of my co-factors (a twice covalently linked heme) 
did not refine properly, which is why i switched the refinement to CCP4 
and used REFMAC. What I initially did not know is that REFMAC and 
STARANISO do not go well together when it comes to the Rfree-flags in 
the diffraction cut-off regions. 


I went back and tried to use SFtools by CCP4 as described on 
https://staraniso.globalphasing.org/test_set_flags_about.html
 to generate a staraniso_mtz suitable for refinement in REFMAC, phased 
it again with my initial model and ran a refinement cycle, because I 
thought skipping a program might be a good idea. However I do not know 
if the mtz file I get has the appropriate column labels and also I do 
not know how to convert it to an mmcif that includes the data from processing. 
i have never before tried to 
combine AUTOPROC-processed data with REFMAC data and am not very 
familiar with REFMAC to begin with. I have tried the sftool server to validate 
the mtz from REFMAC processing but I get an error message 

Converting SF file to mmcif format ... 
Warning: (data block=1): all status (80493) are assigned as 'x' (changed! 
'x'->'o')
Error: File () has no mandatory items 'F/I/F+/F-/I+/I-' (data block=1)

I 
tried to use Phenix (as it automatically converts the mtz to an mmcif 
file) by running a "mock"-refinement with fixed coordinates but the 
mmcif file I get out of this seems to contain some wrongly labeled data 
fields in block 1 when I try to upload it to PDBs validation server. 

Essentially it seems to contain some 3 data points in block 1 that have a ? 
This is the error message I receive:


Warning:
 (data block=1): 30301 reflections have status assigned as '?' (changed 
to 'x') Warning: (data block=1): 30301 reflections have wrong status. 
Not in list(o,f,x,-,<,h,l) Warning: No wavelength value was found in 
SF file (data block=1).

which is essentially the same as above, so I guess it is derived from the same 
problem.


I would be very 
grateful for any help. 


Cheers and thanks, Vera



To unsubscribe from the CCP4BB list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/WA-JISC.exe?SUBED1=CCP4BB=1

This message was issued to members of www.jiscmail.ac.uk/CCP4BB, a mailing list 
hosted by www.jiscmail.ac.uk, terms & conditions are available at 
https://www.jiscmail.ac.uk/policyandsecurity/

Lucene 9.3.0 release

2022-07-11 Thread 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

[jira] [Commented] (LUCENE-10396) Automatically create sparse indexes for sort fields

2022-06-28 Thread Ignacio Vera (Jira)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ignacio Vera commented on  LUCENE-10396  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Automatically create sparse indexes for sort fields   
 

  
 
 
 
 

 
 I think you are assuming that we always visit all terms in the index. The iteration might be driven by the result of a query that contains a subset of the documents. In pseudo-code would look like: 

 

DocIdSetIterator iterator = executeQuery();
SortedDocValues sortedDocValues = getSortedDocValues();
int doc = iterator.nextDoc();
while (doc != DocIdSetIterator.NO_MORE_DOCS) {
if (sortedDocValues.advanceExact(doc)) {
BytesRef bytesRef = sortedDocValues.lookupOrd(sortedDocValues.ordValue());
consume(bytesRef);
// advance our iterator to the next document with different ordinal
doc = iterator.advance(sortedDocValues.advanceOrd());
} else {
doc = iterator.nextDoc();
}
}
 

 I don't see how to do this efficiently with the inverted index only.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)

[jira] [Commented] (LUCENE-10396) Automatically create sparse indexes for sort fields

2022-06-28 Thread Ignacio Vera (Jira)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ignacio Vera commented on  LUCENE-10396  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Automatically create sparse indexes for sort fields   
 

  
 
 
 
 

 
 More exactly, the SortedDocValues iterator might have been advanced to a different ordinal.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)

[jira] [Commented] (LUCENE-10396) Automatically create sparse indexes for sort fields

2022-06-28 Thread Ignacio Vera (Jira)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ignacio Vera commented on  LUCENE-10396  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Automatically create sparse indexes for sort fields   
 

  
 
 
 
 

 
 > The slowness is probably the lookupOrd? Can you avoid this? Just next() the termsenum to move on to the next ord. Not really because the call to advance can move the SortedDocValues iterator to a different ordinal. We need to position our TermsEnum in each call. That's one of the advantage of my proposal as everything advances together. > I'd also modify the call to termsEnum.postings() to be termsEnum.postings(postingsEnum, PostingEnum.NONE) I will try that and I will report back.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)

[jira] [Commented] (LUCENE-10396) Automatically create sparse indexes for sort fields

2022-06-28 Thread Ignacio Vera (Jira)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ignacio Vera commented on  LUCENE-10396  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Automatically create sparse indexes for sort fields   
 

  
 
 
 
 

 
 Here is the code I am using when using postings/TermsEnum from the inverted index which might be totally wrong / inefficient as unfortunately I am not an expert in this area: 

 

// position the terms enum on the current term
termsEnum.seekExact(sortedDocValues.lookupOrd(sortedDocValues.ordValue()));
// advance
if (termsEnum.next() == null) {
doc = sortedDocValues.advance(DocIdSetIterator.NO_MORE_DOCS);
} else {
termsEnum.postings(postingsEnum);
doc = sortedDocValues.advance(postingsEnum.nextDoc());
}

 

 This code performs ok for lower cardinality but it becomes slow for high cardinality. Similar to what I have done in the linked PR, I have indexed 50 million documents in a sorted index. The documents contain a SortedDocValues with a 10 bytes term and the term is indexed using a StringField as well. I checked the index size and the speed of retrieving the first document per term with different cardinalities and the results looks like:  1000 cardinality INDEX SIZE: 6.110762596130371 MB Average: 0.00264192705 seconds  1 cardinality INDEX SIZE: 22.32368278503418 MB Average: 0.01891452695003 seconds  10 cardinality INDEX SIZE: 86.16338920593262 MB Average: 0.1449143188 seconds  50 cardinality INDEX SIZE: 108.61055660247803 MB Average: 0.4431338875005 seconds  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)

[jira] [Commented] (LUCENE-10396) Automatically create sparse indexes for sort fields

2022-06-28 Thread Ignacio Vera (Jira)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ignacio Vera commented on  LUCENE-10396  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Automatically create sparse indexes for sort fields   
 

  
 
 
 
 

 
 If I understand you correct, you mean leveraging the inverted index to get the first document per term.  I tried that and my conclusion was that it was slower than manually iterate the doc values.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)

[jira] [Commented] (LUCENE-10396) Automatically create sparse indexes for sort fields

2022-06-24 Thread Ignacio Vera (Jira)



[ 
https://issues.apache.org/jira/browse/LUCENE-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17558474#comment-17558474
 ] 

Ignacio Vera commented on LUCENE-10396:
---

I open a draft PR that shows the idea I exposed above.

> Automatically create sparse indexes for sort fields
> ---
>
> Key: LUCENE-10396
> URL: https://issues.apache.org/jira/browse/LUCENE-10396
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Adrien Grand
>Priority: Minor
> Attachments: sorted_conjunction.png
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> On Elasticsearch we're more and more leveraging index sorting not as a way to 
> be able to early terminate sorted queries, but as a way to cluster doc IDs 
> that share similar properties so that queries can take advantage of it. For 
> instance imagine you're maintaining a catalog of cars for sale, by sorting by 
> car type, then fuel type then price. Then all cars with the same type, fuel 
> type and similar prices will be stored in a contiguous range of doc IDs. 
> Without index sorting, conjunctions across these 3 fields would be almost a 
> worst-case scenario as every clause might match lots of documents while their 
> intersection might not. With index sorting enabled however, there's only a 
> very small number of calls to advance() that would lead to doc IDs that do 
> not match, because these advance() calls that do not lead to a match would 
> always jump over a large number of doc IDs. I had created that example for 
> ApacheCon last year that demonstrates the benefits of index sorting on 
> conjunctions. In both cases, the index is storing the same data, it just gets 
> different doc ID ordering thanks to index sorting:
> !sorted_conjunction.png!
> While index sorting can help improve query efficiency out-of-the-box, there 
> is a lot more we can do by taking advantage of the index sort explicitly. For 
> instance {{IndexSortSortedNumericDocValuesRangeQuery}} can speed up range 
> queries on fields that are primary sort fields by performing a binary search 
> to identify the first and last documents that match the range query. I would 
> like to introduce [sparse 
> indexes|https://en.wikipedia.org/wiki/Database_index#Sparse_index] for fields 
> that are used for index sorting, with the goal of improving the runtime of 
> {{IndexSortSortedNumericDocValuesRangeQuery}} by making it less I/O intensive 
> and making it easier and more efficient to leverage index sorting to filter 
> on subsequent sort fields. A simple form of a sparse index could consist of 
> storing every N-th values of the fields that are used for index sorting.
> In terms of implementation, sparse indexing should be cheap enough that we 
> wouldn't need to make it configurable and could enable it automatically as 
> soon as index sorting is enabled. And it would get its own file format 
> abstraction.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

[jira] [Comment Edited] (LUCENE-10396) Automatically create sparse indexes for sort fields

2022-06-23 Thread Ignacio Vera (Jira)



[ 
https://issues.apache.org/jira/browse/LUCENE-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17558103#comment-17558103
 ] 

Ignacio Vera edited comment on LUCENE-10396 at 6/23/22 3:01 PM:


I have been thinking on the ability if visiting a single documents per field 
value as explained for Adrien above and I think we can implement it in a not 
intrusive way for SortedDocValues that have low cardinality. The idea is to add 
the following method to the SortedDocValues api with a default implementation:

{code}
  /**
   * Advances the iterator the the next document whose ordinal is distinct to 
the current ordinal
   * and returns the document number itself. It returns {@link
   * #NO_MORE_DOCS} if there is no more ordinals distinct to the current one 
left.
   *
   * The behaviour of this method is undefined when called after the 
iterator has exhausted and may result in unpredicted behaviour.
   *  
   * The default implementation just iterates over the documents and manually 
checks if the ordinal has changed but
   *  but some implementations are  considerably more efficient than that.
   *
   */
  public int advanceOrd() throws IOException {
int doc = docID();
if (doc == DocIdSetIterator.NO_MORE_DOCS) {
  return doc;
}
final long ord = ordValue();
do  {
  doc = nextDoc();
} while (doc != DocIdSetIterator.NO_MORE_DOCS && ordValue() == ord);
assert doc == docID();
return doc;
  }
{code}

When consuming the doc values, if the field is the primary sort of he index and 
the cardinality is low (average of documents per field >64?), then we will use 
a DirectMonotonicWriter to write the offset for each ord which should not use 
too much disk space. When producing the doc value, we will override this method 
with a faster DirectMonotonicReader implementation.





was (Author: ivera):
I have been thinking on the ability if visiting a single documents per field 
value as explained for Adrien above and I think we can implement it in a not 
intrusive way for SortedDocValues that have low cardinality. The idea is to add 
the following method to the SortedDocValues api with a default implementation:

{code}
  /**
   * Advances the iterator the the next document whose ordinal is distinct to 
the current ordinal
   * and returns the document number itself. Exhausts the iterator and returns 
{@link
   * #NO_MORE_DOCS} if there is no more ordinals distinct to the current one.
   *
   * The behaviour of this method is undefined when called with 
 target  current
   * , or after the iterator has exhausted. Both cases may result in 
unpredicted behaviour.
   *  
   * The default implementation just iterates over the documents and manually 
checks if the ordinal has changed but
   *  but some implementations are  considerably more efficient than that.
   *
   */
  public int advanceOrd() throws IOException {
int doc = docID();
if (doc == DocIdSetIterator.NO_MORE_DOCS) {
  return doc;
}
final long ord = ordValue();
do  {
  doc = nextDoc();
} while (doc != DocIdSetIterator.NO_MORE_DOCS && ordValue() == ord);
assert doc == docID();
return doc;
  }
{code}

When consuming the doc values, if the field is the primary sort of he index and 
the cardinality is low (average of documents per field >64?), then we will use 
a DirectMonotonicWriter to write the offset for each ord which should not use 
too much disk space. When producing the doc value, we will override this method 
with a faster DirectMonotonicReader implementation.




> Automatically create sparse indexes for sort fields
> ---
>
> Key: LUCENE-10396
> URL: https://issues.apache.org/jira/browse/LUCENE-10396
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Adrien Grand
>Priority: Minor
> Attachments: sorted_conjunction.png
>
>
> On Elasticsearch we're more and more leveraging index sorting not as a way to 
> be able to early terminate sorted queries, but as a way to cluster doc IDs 
> that share similar properties so that queries can take advantage of it. For 
> instance imagine you're maintaining a catalog of cars for sale, by sorting by 
> car type, then fuel type then price. Then all cars with the same type, fuel 
> type and similar prices will be stored in a contiguous range of doc IDs. 
> Without index sorting, conjunctions across these 3 fields would be almost a 
> worst-case scenario as every clause might match lots of documents while their 
> intersection might not. With index sorting enabled however, there's only a 
> very small number of calls to advance() that would lead to doc IDs that do 
> not match, because these advance() calls that do not lead

[jira] [Commented] (LUCENE-10396) Automatically create sparse indexes for sort fields

2022-06-23 Thread Ignacio Vera (Jira)



[ 
https://issues.apache.org/jira/browse/LUCENE-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17558103#comment-17558103
 ] 

Ignacio Vera commented on LUCENE-10396:
---

I have been thinking on the ability if visiting a single documents per field 
value as explained for Adrien above and I think we can implement it in a not 
intrusive way for SortedDocValues that have low cardinality. The idea is to add 
the following method to the SortedDocValues api with a default implementation:

{code}
  /**
   * Advances the iterator the the next document whose ordinal is distinct to 
the current ordinal
   * and returns the document number itself. Exhausts the iterator and returns 
{@link
   * #NO_MORE_DOCS} if there is no more ordinals distinct to the current one.
   *
   * The behaviour of this method is undefined when called with 
 target  current
   * , or after the iterator has exhausted. Both cases may result in 
unpredicted behaviour.
   *  
   * The default implementation just iterates over the documents and manually 
checks if the ordinal has changed but
   *  but some implementations are  considerably more efficient than that.
   *
   */
  public int advanceOrd() throws IOException {
int doc = docID();
if (doc == DocIdSetIterator.NO_MORE_DOCS) {
  return doc;
}
final long ord = ordValue();
do  {
  doc = nextDoc();
} while (doc != DocIdSetIterator.NO_MORE_DOCS && ordValue() == ord);
assert doc == docID();
return doc;
  }
{code}

When consuming the doc values, if the field is the primary sort of he index and 
the cardinality is low (average of documents per field >64?), then we will use 
a DirectMonotonicWriter to write the offset for each ord which should not use 
too much disk space. When producing the doc value, we will override this method 
with a faster DirectMonotonicReader implementation.




> Automatically create sparse indexes for sort fields
> ---
>
> Key: LUCENE-10396
> URL: https://issues.apache.org/jira/browse/LUCENE-10396
> Project: Lucene - Core
>  Issue Type: Task
>Reporter: Adrien Grand
>Priority: Minor
> Attachments: sorted_conjunction.png
>
>
> On Elasticsearch we're more and more leveraging index sorting not as a way to 
> be able to early terminate sorted queries, but as a way to cluster doc IDs 
> that share similar properties so that queries can take advantage of it. For 
> instance imagine you're maintaining a catalog of cars for sale, by sorting by 
> car type, then fuel type then price. Then all cars with the same type, fuel 
> type and similar prices will be stored in a contiguous range of doc IDs. 
> Without index sorting, conjunctions across these 3 fields would be almost a 
> worst-case scenario as every clause might match lots of documents while their 
> intersection might not. With index sorting enabled however, there's only a 
> very small number of calls to advance() that would lead to doc IDs that do 
> not match, because these advance() calls that do not lead to a match would 
> always jump over a large number of doc IDs. I had created that example for 
> ApacheCon last year that demonstrates the benefits of index sorting on 
> conjunctions. In both cases, the index is storing the same data, it just gets 
> different doc ID ordering thanks to index sorting:
> !sorted_conjunction.png!
> While index sorting can help improve query efficiency out-of-the-box, there 
> is a lot more we can do by taking advantage of the index sort explicitly. For 
> instance {{IndexSortSortedNumericDocValuesRangeQuery}} can speed up range 
> queries on fields that are primary sort fields by performing a binary search 
> to identify the first and last documents that match the range query. I would 
> like to introduce [sparse 
> indexes|https://en.wikipedia.org/wiki/Database_index#Sparse_index] for fields 
> that are used for index sorting, with the goal of improving the runtime of 
> {{IndexSortSortedNumericDocValuesRangeQuery}} by making it less I/O intensive 
> and making it easier and more efficient to leverage index sorting to filter 
> on subsequent sort fields. A simple form of a sparse index could consist of 
> storing every N-th values of the fields that are used for index sorting.
> In terms of implementation, sparse indexing should be cheap enough that we 
> wouldn't need to make it configurable and could enable it automatically as 
> soon as index sorting is enabled. And it would get its own file format 
> abstraction.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

Re: [Geoserver-users] GeoServer 2.21 - Admin and Proxy Base Url

2022-06-14 Thread Vera Green

I am also proxying tomcat to Apache https to have a nice url without the
port, so from 8080 to 80 ( 442). For me, the global setting worked for the
proxy but I believe I could still go through tomcat (xxx:8080) prior to
closing the port. Might be a workaround.

If you can't get around it, geoserver is all just XML, you can write a bash
script to set the setting in your workspaces. Back up first 藍.

I little curious why you need this though. My servers are headless Linux so
I can't test localhost unfortunately.

Vera


On Fri., Jun. 10, 2022, 1:58 a.m. Mattias Andrén via Geoserver-users, <
geoserver-users@lists.sourceforge.net> wrote:

> Thanks Graham,
>
>
>
> I will try this.
>
>
>
> I would prefer to have a global setting for this since I have 62
> workspaces which I really don’t want to enable local settings for.
>
>
>
> Is it possible to add a global setting to enable the old behavior
> regarding this?
>
>
>
> Regards
>
>
>
> *Mattias Andrén *
>
>
>
> *Från:* Humphries, Graham 
> *Skickat:* den 9 juni 2022 23:45
> *Till:* Mattias Andrén ;
> geoserver-users@lists.sourceforge.net
> *Ämne:* RE: GeoServer 2.21 - Admin and Proxy Base Url
>
>
>
> Hi Mattias,
>
>
>
>
>
> FYI I have deployed Geoserver 2.21.0 into my test environment. This has a
> similar setup to what you describe, except the reverse proxying is handled
> by Apache HTTPD running on Unix.
>
>
>
> To stop the admin pages being redirected I removed the Global setting for
> the Proxy base URL and have only applied it in the individual workspace
> settings.
>
>
>
> Cheers,
>
> Graham
>
>
>
> *From:* Mattias Andrén via Geoserver-users <
> geoserver-users@lists.sourceforge.net>
> *Sent:* Thursday, 9 June 2022 10:54 PM
> *To:* geoserver-users@lists.sourceforge.net
> *Subject:* [Geoserver-users] GeoServer 2.21 - Admin and Proxy Base Url
>
>
>
> Hi,
>
>
>
> I’m trying to upgrade from Geoserver 2.18 to 2.21 on my test server. I
> have been using this version on my dev server without issue.
>
>
>
> I’m using IIS URL Rewrite as a reverse proxy. As a consequence I have set
> the Proxy Base URL in the Geoserver Global Settings to match.
>
> This has been working  without issue in previous versions and the Admin
> interface uses the local URL. My production server is running version
> 2.18.0 with this configuration.
>
>
>
> If I have the Proxy Base URL set in my test instance the Admin interface
> applies the Proxy Base URL (from the Global Settings page) to all the pages
> in the Admin interface.
>
> In previous version (i.e 2.18) the Admin interface did not apply the Proxy
> Base URL and you could use the Admin interface on the server using
> http://localhost:8080/geoserver
>
>
>
> Is it possible to alter this behavior and revert it back to how it worked
> before?
>
>
>
> Se also the question posted by Graham Humphries
>
> https://sourceforge.net/p/geoserver/mailman/message/37250476/
> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fgeoserver%2Fmailman%2Fmessage%2F37250476%2F=05%7C01%7Cmattias.andren%40varberg.se%7Cff3ec1b59b1f49245ec408da4a614342%7C7f8b8c7bffd84804914cfac1638c3f65%7C0%7C0%7C637904078873728030%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=ridXOTAydSyxd3dKeJ%2FUtk1BIeB6C%2FPYooC4BNuozcY%3D=0>
>
>
>
>
>
> Regards
>
> *Mattias Andrén*
>
>
>
>
> --
>
>
> CONFIDENTIALITY NOTICE AND DISCLAIMER
> The information in this transmission may be confidential and/or protected
> by legal professional privilege, and is intended only for the person or
> persons to whom it is addressed. If you are not such a person, you are
> warned that any disclosure, copying or dissemination of the information is
> unauthorised. If you have received the transmission in error, please
> immediately contact this office by telephone, fax or email, to inform us of
> the error and to enable arrangements to be made for the destruction of the
> transmission, or its return at our cost. No liability is accepted for any
> unauthorised use of the information contained in this transmission.
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, al

[jira] [Resolved] (LUCENE-10604) Improve ability to test and debug triangulation algorithm in Tessellator

2022-06-09 Thread Ignacio Vera (Jira)



 [ 
https://issues.apache.org/jira/browse/LUCENE-10604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ignacio Vera resolved LUCENE-10604.
---
Fix Version/s: 9.3
 Assignee: Ignacio Vera
   Resolution: Fixed

Thanks Craig!

> Improve ability to test and debug triangulation algorithm in Tessellator
> 
>
> Key: LUCENE-10604
> URL: https://issues.apache.org/jira/browse/LUCENE-10604
> Project: Lucene - Core
>  Issue Type: Test
>  Components: core/other
>Reporter: Craig Taverner
>Assignee: Ignacio Vera
>Priority: Minor
>  Labels: geo, pull-request-available
> Fix For: 9.3
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> While working on https://issues.apache.org/jira/browse/LUCENE-10563, it was 
> found to be extremely difficult to debug the inner workings of the 
> triangulation algorithm in the Tessellator class. To make things easier, we 
> made use of a monitor interface that tests could use to instrument the 
> algorithm and receive detailed information on the state of the algorithms 
> progress. This issue requests that this interface and a test implementation 
> of it be included in Lucene to facilitate future bug-fixing of this complex 
> algorithm.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

1 2 3 4 5 6 7 8 9 10 >

1 - 100 of 12184 matches

Mail list logo