The Rare Bug with GeoUtils May have Been Fixed in Lucene `8.5.1`

[MarcusSorealheis]

Describe the bug For a tangentially related project, I started to look through the Twitter source code for geospatial search queries and I came across this method that looked slightly familiar:

https://github.com/twitter/the-algorithm/blob/138bb519975407d4ea0dc1478d897d451ef05dab/src/java/com/twitter/search/earlybird/search/GeoQuadTreeQueryBuilder.java#L153-L167

Additional context

While not exactly the same issue in the wild, Lucene users recently observed an issue with tessellation of collinear edges - LUCENE-9251. I don't think that it is a common bug or pervasive, given many users have upgraded or were not tessellating on the same line. I do wonder if this issue was resolved by that big fix.

What version of Lucene are you all running? It seems like it's a fork, sort of, but also maybe 7.x or 8.x? I would be happy to try to propose a fix if that's not what this rare bug is related to.

[MarcusSorealheis]

Also, are we sure this only happens on occasion? I believe that would suggest a different problem.

[aloiscochard]

Thanks @MarcusSorealheis for sharing your discovery.

I'm not sure if it happens only on occasion, anyway for future reference, if anyone feels like doing further analysis, here is the relevant code: https://github.com/apache/lucene-solr/commit/c313365

[thegu5]

@aloiscochard why are you pretending to be a twitter employee :skull:

[MarcusSorealheis]

I don't think they did that. i think they just clicked the links inside the link I shared. I don't think they are a neutral addition. I'm not confident that this is indeed the issue.