-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove ORM 6.2 upgrade job since 7.0 targets 6.3+ #3746
Remove ORM 6.2 upgrade job since 7.0 targets 6.3+ #3746
Conversation
- since this bug is not fixed we constantly need to bump the version and also the bug is in their main branch leading to failures in upgrade test runs. We are subscribed to the issue, so once it is resolved, we can change the condition.
The Elasticsearch build failed with the usual error "not supporting extreme scaled numeric values" as that bug is not fixed yet. |
We're talking about this one, I assume:
This could be a regression in Lucene 10.0.0-SNAPSHOT, especially since there's been a change in this class recently: apache/lucene@d633c9b . Ironically, the problem that patch fixed looks a lot like the stacktrace above. This could be also a bug in our code that happens only with a certain index fragment topology (documents spear among fragments a certain way), which could make the bug timing-sensitive. But I'd save that theory for last, because that will be very difficult to debug.
Line 179 in 5fccd1a
|
Please ignore this, I obviously can't read 😓 It's a different constant. |
Mooooonday 😃 |
I think there might be a bug there (or in code that relies on this): Lines 96 to 99 in 077ac00
I'll send a PR. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
I'll look into other failed branches, so opening this as a draft for now