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
yes, the way it works is that there is a bounded queue (ring buffer) with the capacity as template parameter.
When the existing ring buffer is full another new empty ring buffer gets allocated to emplace there the message. However, the capacity of the queue (ring buffer) is always the same as the one specified during compilation and the log message cannot exceed the capacity of the bounded buffer.
This seemed like a limitation to me so there is a fix for it in master and also v2.6.0.
The unbounded queue will now resize to a capacity that is at least the size of the message.
The initial size of the unbounded queue is also configurable in runtime now and no longer needed to recompile.
I got the above error message. Does that mean my log message is too long so that the ring buffer can not hold the message?
The text was updated successfully, but these errors were encountered: