Releases · Abc-Arbitrage/ZeroLog

Fixed silent allocations which could occur when more than 10 Append calls were issued.
Added a LogEventArgumentCapacity option which sets the max count of expected Append calls. The default value is 32.
Added a LogEventArgumentExhaustionStrategy option which controls what to do when too many Append calls are issued. Messages can either be truncated (default behavior) or cause allocations.
Added a global TruncatedMessageSuffix option which controls the suffix which will be appended to a truncated message. Default value: " [TRUNCATED]".
Refactored configuration options. There is a breaking change in a public interface that should have remained internal and is not expected to be implemented outside of ZeroLog, hence only the minor version is increased.
Fixed an access violation that could occur if a logger is used after a call to LogManager.Shutdown. Note that this could still happen if a log event is acquired before the shutdown and is retained for more than 100ms before Append is called, but this is incorrect ZeroLog usage and is not expected. Log events acquired after the shutdown are safe.
Fixed an error that caused ZeroLog to shutdown when a message longer than 16KB was logged. Such messages will either be truncated or cause an error to be logged.

Assets 3

29 Aug 17:16

ltrzesniewski

v1.2.0

b49f2db

v1.2.0

Many optimizations
Automatic flushing at the end of a log burst. Can be disabled with LogManager.Config.FlushAppenders
Added LogManager.GetLogger<T>()
Remove shutdown timeout which caused access violations with large buffers

Note that this release changes the API surface of appenders. It didn't get a major version bump as it should not be a breaking change for most users (it will only break if you use custom appenders). More API changes will be made in v2.0.

Assets 3