-
Notifications
You must be signed in to change notification settings - Fork 563
Integer overflow in bean ordering causes inadvertent prioritization #2477
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
Comments
therepanic
added a commit
to therepanic/spring-data-rest
that referenced
this issue
May 9, 2025
…rojects#2477) Signed-off-by: Andrey Litvitski <[email protected]>
mp911de
pushed a commit
that referenced
this issue
May 13, 2025
Signed-off-by: Andrey Litvitski <[email protected]> Closes: #2477 Original pull request: #2478
mp911de
pushed a commit
that referenced
this issue
May 13, 2025
Signed-off-by: Andrey Litvitski <[email protected]> Closes: #2477 Original pull request: #2478
mp911de
pushed a commit
that referenced
this issue
May 13, 2025
Signed-off-by: Andrey Litvitski <[email protected]> Closes: #2477 Original pull request: #2478
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Error is here
The
RepositoryRelProvider
uses the order withOrdered.LOWEST_PRECEDENCE + 10
, indicating lower then the intended lowest precedence. Since the lowest precedence isInteger.MAX_VALUE
, this rolls back to a value nearInteger.MIN_VALUE
, causing this class to have extremely high precedence.In all likelihood the intended behavior was low but not minimal ordering, i.e.
Ordered.LOWEST_PRECEDENCE - 10
.The text was updated successfully, but these errors were encountered: