You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem description
If the serializers default configuration is changed then a WARNING is written into the log to make sure if this is really meant to be changed. However if the change was indeed the intend, there is no possibility to switch off further notifications about this "problem" to keep focus on other possible unintended issues.
Possible solution
The desired solution would be to add a switch to disable this behavior. The default should be "on" (logging the possible issue at first sight).
Considered alternatives
The alternative of increasing the log level is not a reasonable solution (although you get rid of the serializer change messages) because this also hides notifications about other (unitended) issues, too.
I was not able to disable logging (through logger config) only for this class, but even if it would have worked... are there any other important notifications that could possibly swallowed without intention?
Additional context
The log messages to be suppressed are located within the Serialization class at
* Fix for issue #6377
* created a setting property LogSerializerOverrideOnStart to reflect if warning should be logged or not
* updated default config to enable logging for this issue by default
* added property to the configuration Spezifikation
* added API approvals
---------
Co-authored-by: Aaron Stannard <aaron@petabridge.com>
Problem description
If the serializers default configuration is changed then a WARNING is written into the log to make sure if this is really meant to be changed. However if the change was indeed the intend, there is no possibility to switch off further notifications about this "problem" to keep focus on other possible unintended issues.
Possible solution
The desired solution would be to add a switch to disable this behavior. The default should be "on" (logging the possible issue at first sight).
Considered alternatives
The alternative of increasing the log level is not a reasonable solution (although you get rid of the serializer change messages) because this also hides notifications about other (unitended) issues, too.
I was not able to disable logging (through logger config) only for this class, but even if it would have worked... are there any other important notifications that could possibly swallowed without intention?
Additional context
The log messages to be suppressed are located within the Serialization class at
akka.net/src/core/Akka/Serialization/Serialization.cs
Line 333 in 8dfa8f8
The text was updated successfully, but these errors were encountered: