Files
PrismLauncher/tests
umutcagand 6bc731da54 fix(logs): read log4j event timestamps as milliseconds
log4j's XMLLayout writes the event time in milliseconds since the epoch, but
parseAttributes() handed it to QDateTime::fromSecsSinceEpoch(). Every entry in
the Minecraft Log tab therefore carried an instant about 55000 years out, and
once rendered as HH:mm:ss it showed a clock time with no relation to when the
line was actually logged.

The launcher's own sample log shows it plainly: the first two events of
testdata/TestLogs/vanilla-1.21.5.xml.log are stamped 1745005148589 and
1745005150587, just under two seconds apart, which is also how far apart they
are in the plain text capture of the same startup sequence. Read as seconds
they land 33 minutes apart, in the year 57267.

The added test compares instants rather than rendered clock times, so it does
not depend on the time zone it runs in.

Assisted-by: Claude Code:claude-opus-5
Signed-off-by: umutcagand <237324081+c8dhjp4tyv-bit@users.noreply.github.com>
2026-09-12 10:11:48 +03:00
..
2025-09-15 18:25:07 +03:00
2024-12-19 10:42:42 +02:00
2023-08-14 18:16:53 +02:00
2023-08-14 18:16:53 +02:00
2023-08-14 18:16:53 +02:00
2023-08-14 18:16:53 +02:00
2026-05-13 10:18:55 +03:00
2023-08-14 18:16:53 +02:00
2023-08-14 18:16:53 +02:00
2026-04-03 14:39:27 +03:00
2023-08-14 18:16:53 +02:00