-
Notifications
You must be signed in to change notification settings - Fork 616
Test against Java 20 in CI. #2701
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
Do you need input from us on that one @gregturn ? |
I'll let you know if I run into anything. |
I took at shot at pushing a Jenkins update that would run on Java 20, but it failed twice. You can see the latest one at https://jenkins.spring.io/blue/organizations/jenkins/spring-data-neo4j/detail/main/1245/pipeline/ (let me know if you can't). The details are in the latest commit on https://github.com/spring-projects/spring-data-neo4j/tree/issue/java20. (I had to test it on the main branch, but pulled back from that and moved the work to this side branch). I'm frankly not certain WHAT is causing the grief. FYI: I have been using this version of Java 20 locally for test purposes.
If you wish to run the test suite locally against |
My analysis of this: In @Bean
ReactiveBeforeBindCallback<ImmutablePersonWithAssignedId> valueChange() {
return entity -> {
entity.someValue = SOME_VALUE_VALUE;
return Mono.just(entity);
};
} matching The failure occurs when persisting a
Sorry for the screenshots, but that's easier to reformat the reactive stack traces here. This is the stack for JDK 17 when ending up in this case: JDK 20 acts totally different I am unsure if Spring Data Commons must fix this in Update: This is the simplest test to reproduce it with any JDK 20 (I used Azul) cc @mp911de |
@gregturn I don't think its Project reactor. It's the |
Thanks @michael-simons. We've since solved this, and I've verified building Spring Data Neo4j against Java 20. |
No description provided.
The text was updated successfully, but these errors were encountered: