-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Don't re-initialize ThreadLocalRandom in GraalVM > 20.2 #12344
Conversation
234718b
to
6bda026
Compare
6bda026
to
d98e117
Compare
As of oracle/graal@1b7b2c8 reinitialization of ThreadLocalRandom causes failures in native image builds (see oracle/graal#2841). Additionally as of oracle/graal#2790 Quarkus doesn't need to manually reinitialize ThreadLocalRandom.
d98e117
to
51fc58b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Please refrain from having behavior changes and refactorings in the same commit. It makes things very hard to review. |
Noted. For the record the behavior changes in this PR are https://github.com/quarkusio/quarkus/pull/12344/files#diff-99b0ae6b0ce4104e45b9c9d5f6d3b8a6L669-R668 anything else is refactoring to reduce code duplication. |
@zakkak I understand that this should be backported as it's affecting current stable versions with GraalVM 20.2. Am I right? Thanks. |
Well one could indeed skip the explicit re-initialization with 20.2, but would need to enable the This PR only skips re-initialization for GraalVM > 20.2 since 20.3 will feature HTH |
OK, let's not backport it then. Thanks. |
As of oracle/graal@1b7b2c8 reinitialization of ThreadLocalRandom causes failures in native image
builds (see oracle/graal#2841).
Additionally as of oracle/graal#2790 Quarkus doesn't need to manually reinitialize ThreadLocalRandom.