Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Burn discovered in one case that substituting into the message with a value which looked like {name} caused an exception.
Investigation revealed that the message was being substituted into twice.
Investigation also revealed some logging paths wrongly substituted using the {} style instead of the {n} style. Fix both of these on all logger variants.