-
Notifications
You must be signed in to change notification settings - Fork 38.3k
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
Remove System.out calls in PreComputeFieldFeature #30571
Comments
I agree those logs introduce too much noise. Since without that we have no way to know the fields initialized at build time, and it has be proven useful in a few recent issues, maybe we can silent that by default, and enable such logging based on a system property? Also should we do this change only as of |
This looks like a change that we can make in M1. This gives the community a chance to provide feedback on whatever mechanism we put in place to add the logging back. |
Logging has been removed by default and can be restored by passing |
Isn't that a bit odd to call that |
Yes this is a Spring-related If you want to propose a better option, please let me know. |
As discussed, let's use |
This commit changes the Java system property used to control PreComputeFieldFeature verbose logging from spring.aot.precompute to spring.native.precompute.log in order to clarify its purpose and avoid confusion with AOT processing of JVM bytecode or Java sources. See spring-projectsgh-30571
While logging information at the
System.out
level in thePreComputeFieldFeature
was a conscious choice until oracle/graal#4669 was implemented, it seems that the information displayed is very verbose:Unless we find a way to activate those logs with a debug flag, we should probably silence this as it doesn't provide much value to users and hasn't been helpful in the past for investigating on issues.
The text was updated successfully, but these errors were encountered: