Set formatter on all broadcasted loggers #1361
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a formatter is set for the broadcast logger, also set that same formatter for all the loggers that it broadcasts to.
Before this change, the already-formatted message would be passed on to the broadcasted loggers, which would format it once again.
This issue was masked by the tests matching the resulting log line using
a_string_starting_with
, which I introduced in #1351 to smooth out differences between our custom instrumentation of tagged logging, since removed, and that ofActiveSupport::TaggedLogging
. Ensure all matching is done against specific strings.Fixes issue #1360, in which the twice-applied formatting causes additional newlines to appear in the message emitted by the broadcasted loggers.