-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
jhipster jdl reactive-ms fails e2e tests #14196
Comments
@mraible : I afraid it's related to migration to Spring Boot 2.4. For each minor version of Spring Boot, there are so much changes. That's why it's not so easy : remember Spring Boot 2.2 -> 2.3, and now 2.3 -> 2.4 |
Trying it manually results in an 404 for the post request. Looking into it. EDIT Looks like something went wrong during generation. |
Did not get any further on saturday, as it seemed to work after everything was generated correctly. Will try again today. |
It seems from spring-data-neo4j 6.0.3 -> 6.0.4/6.0.5 a blocking call was added to |
@atomfrede Can we downgrade spring-data-neo4j as a workaround? |
Looking into it right now. For gradle this works: implementation('org.springframework.data:spring-data-neo4j') {
version {
strictly '6.0.3'
}
} But the protractor tests are failing (which are not related to backend things). Cypress is just working fine. Should we downgrade for now until the potential upstream is fixed? |
Data-neo4j 6.0.6 will be released next week containing the needed fix. Thanks @meistermeier for fixing it that fast. |
don't hesitate to ping me once everything related to neo4j is fixed @atomfrede |
|
I tried the steps in this issue and all tests pass!
Of course, I had to try a couple times. Because Protractor. 😅 |
Is this enough to take Neo4j out of beta? 🧐 |
We have still the issue when using DTOs. Gerrit and me are working on it. The main reason is that the generated entities have cycles. This also makes neo slower than it has to be. But from my point of view we could either prevent DTOs + neo for now or document how to create a workaround (which is ~5 loc) for the current entity and relation structure. |
Although this is already closed, I add my comment here:
(example taken from GH-13797) The problem that were reported in the issue ^^ is rooted in the DTO creation as @atomfrede already pointed out. |
Thanks for clarification. I also think having it uni-directional makes it easier to understand. |
Overview of the issue
When I wrote Reactive Java Microservices with Spring Boot and JHipster (using beta 1), all e2e tests passed. They do not pass with the current
main
branch.Motivation for or Use Case
We should not break things between beta versions.
Reproduce the error
npm link
after cloning themain
branch. Then, create a microservices architecture:Start all the relevant Docker containers.
Start all apps using
./gradlew
.Go into the
gateway
directory and runnpm run e2e
.If you change the gateway to use Cypress, the errors still happen.
Related issues
#14178
Suggest a Fix
Maybe it's caused by this change to Neo4j?
JHipster Version(s)
main
branch. Yes, this is a regression.The text was updated successfully, but these errors were encountered: