-
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
Track configuration initialization state for using loggers #44619
base: main
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
This seems to result in the process freezing after printing the exception... Converting to draft for now. |
False alarm, it only freezes if we pass However, while looking at this I noticed that there is also |
faa7022
to
492fab7
Compare
@radcortez how do you find this idea? |
It's been a while since I looked at how the early boot works with native image generation, but are we using the delayed handler in this case? |
I don't really know, but a quick search led me to quarkus/core/deployment/src/main/java/io/quarkus/deployment/steps/MainClassBuildStep.java Lines 322 to 339 in bbb1009
|
Maybe what we want is a way to dump out the delayed handler queue in the event of error. I know we're able to do that at run time at least, so it should be possible to do so at build time as well? |
Tracks configuration initialization state in a boolean to determine if loggers are ready to be used. Useful when we need to log an error due to an early failure.
Closes #42084