timestamps with zones are not handled correctly

Open tstack opened this issue 3 years ago • 0 comments

lnav version v0.11.0

Describe the bug

With the following logs, the second message does not have the right log_time because the zone is not taken into account. The third message is then seen as being out-of-time-order.

2022-08-27T14:22:01.613Z foo.example.com APP1 1234 Hello, World
2022-08-27T17:22:01.694554+03:00 foo.example.com CRON 20856 - -  (root) CMD (   /usr/bin/nice -n 10 /opt/example/bin/mem_usage_monitor.py >/dev/null 2>&1)
2022-08-27T14:22:01.888Z foo.example.com APP1 4828 Goodbye

Sep 02 '22 17:09 tstack