London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
Hi Matthew
ILog has been a compatibility wrapper for ILogger for quite some time. As a quick-fix you can try using the ILogger interface directly. It should not have this bug.
I found out that a specific version of ILog.WarnFormat does not log at the correct level. This is an odd use case, but I have missed log messages due this bug.
Here's an example code snippet to reproduce:
Here is the output I found in my log file with appropriate settings to show INFO level: