-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
after bumping to 3.0.0.CR2 (a synthetic bean initialized during RUNTIME_INIT) #32566
Comments
/cc @evanchooly (kotlin), @geoand (kotlin) |
Can you please provide a sample project that exhibits the problematic behavior? It's pretty much the only way we can test if the problem still exists in |
tryout repdoruce working on main branch, bump branch:
|
maybe this is the root cause ? i have seed this synthetic message many times and it was always some kind of result of an other error happening under the hood i think.
|
What is |
We'll need a reproducer |
Let's focus on the ArC issue as the rest is due to your migration to ORM 6. @mkouba I wonder if we have an issue with the Dev UI for the scheduler. The Dev UI is consuming See the occurrences of |
i have updated the dangling type annotation to what it should be i guess, as a simple bridging migration solution. but still the issue remains:
|
Hm, so the exception from ArC is Furthermore, it seems that the container is running but was not even fully initialized.
In other words, we don't expect the notification of
|
I believe that you're correct. |
- removes the warning mentioned in the quarkusio#32566
- removes the warning mentioned in the quarkusio#32566
- removes the warning mentioned in the quarkusio#32566 (cherry picked from commit 9a5f479)
- removes the warning mentioned in the quarkusio#32566
@mkouba should this now be closed? |
@punkratz312 Did you manage to solve the |
Closing for lack of feedback |
Describe the bug
after bumping to 3.0.0.CR2 quarki immerse to early an an bean access issue:
The text was updated successfully, but these errors were encountered: