src.text.dmesg: some kernel ring buffer lines can be wrongly sorted by time, leading to a muxer error
The lines of the
dmesg command start with a time. The lines are supposed to be in order of time, but some of them can be at the wrong place.
flt.utils.muxer does not like this and complains that event messages are not sorted by their default clock snapshot value.
It is, in fact, a
src.text.dmesg bug because a message iterator must emit messages in order of time.
If the input is a file, one solution would be to sort the lines first (if not too large), and then emit the messages in this order.
We could also, in all scenarios, skip the lines with a time that is before the last event message's time and warn accordingly.