-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Warning about failing to index Spring class on reload #42237
Comments
/cc @geoand (spring) |
It seems, that 3.12.0 is the first version which is affected, since 3.11.3 is not |
Also add a bit of debugging related to quarkusio/quarkus#42237
- Change all dependencies to the latest versions - Add a bit of debugging related to quarkusio/quarkus#42237 and quarkusio/quarkus#42248 - After 3.13.0 quarkus OTEL exporter uses GRPC streams to export traces. Our hacked together OTEL server could not handle that and was rewritten to conform to OTEL specifications more.
- Change all dependencies to the latest versions - Add a bit of debugging related to quarkusio/quarkus#42237 and quarkusio/quarkus#42248 - After 3.13.0 quarkus OTEL exporter uses GRPC streams to export traces. Our hacked together OTEL server could not handle that and was rewritten to conform to OTEL specifications more.
Hm... When I start the application (before any live reload, I see):
And these warnings make sense as you have not added any JDBC related extensions |
@geoand try to drop "spring-data-jpa" from the creation command (ie make it look like this: |
In that case I see the following on reload:
|
@geoand yes, that is the one I meant. I will change the description to make it more clear |
- Change all dependencies to the latest versions - Add a bit of debugging related to quarkusio/quarkus#42237 and quarkusio/quarkus#42248 - After 3.13.0 quarkus OTEL exporter uses GRPC streams to export traces. Our hacked together OTEL server could not handle that and was rewritten to conform to OTEL specifications more.
- Change all dependencies to the latest versions - Add a bit of debugging related to quarkusio/quarkus#42237 and quarkusio/quarkus#42248 - After 3.13.0 quarkus OTEL exporter uses GRPC streams to export traces. Our hacked together OTEL server could not handle that and was rewritten to conform to OTEL specifications more.
- Change all dependencies to the latest versions - Add a bit of debugging related to quarkusio/quarkus#42237 and quarkusio/quarkus#42248 - After 3.13.0 quarkus OTEL exporter uses GRPC streams to export traces. Our hacked together OTEL server could not handle that and was rewritten to conform to OTEL specifications more.
I've just seen this one. The |
@aureamunoz #42895 is merged and present in 3.14.2, I tested this reproducer with 3.14.4 and the issue is still present. Will you have a look? |
Hi, I just looked at it and I can't reproduce it. Everything works fine for me, I don't have any errors. Do you have the project in question? |
I only saw it in CI when I bumped Quarkus to 3.14.4. Let me try it locally and report back. |
Here are steps to reproduce:
Wait for the app to start and reload it by pressing s or by adding a new class. |
|
No way to reproduce:
This is my env:
|
Just read your logs, there is |
btw @aureamunoz I am glad you are looking into this, thank you |
Oups! |
It appears that the Initially, I added this class to be included in the quarkus-spring-aop module because I didn’t notice the aot distinction. The package name for the class is very similar to the AOP module's and doesn’t include the word "experimental," which led to the confusion. To resolve this, a new Quarkus Spring Experimental project/artifact/dependency will need to be created to support this functionality. |
false alarm, it can be included in the quarkus-spring-core |
PR for fixing this created: #43501 |
Fixes quarkusio#42237 (cherry picked from commit 9cf2c80)
Describe the bug
I have an app, which uses several Spring extensions. When I run in a Dev Mode and do a reload (manually or a by adding a new file) there is a warning in a logs.
This warning emerged after update from 3.11.0 to 3.12.3
Expected behavior
No warnings during reload
Actual behavior
How to Reproduce?
mvn clean quarkus:dev
s
or by adding a new classOutput of
uname -a
orver
6.7.3-200.fc39.x86_64
Output of
java -version
Java version: 21.0.1, vendor: Eclipse Adoptium
Quarkus version or git rev
3.13.0
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Additional information
No response
The text was updated successfully, but these errors were encountered: