maziggy 8c326256db fix(system): emit boot_time and generated_at as tz-aware UTC ...

datetime.fromtimestamp(ts) and datetime.now() return naive local
  datetimes; .isoformat() then emits no tz marker. The frontend's
  parseUTCDate helper appends 'Z' to bare strings, treats the value
  as UTC, then converts to local for display — applying the local
  offset twice. Reporter on UTC+3 saw boot_time +3h ahead while
  uptime was correct (uptime is a backend-side delta of two
  naive-local values, so the missing tz info cancels out).

  Fix: pass tz=timezone.utc to datetime.fromtimestamp and
  datetime.now in system.py's boot_time / uptime path, plus the two
  adjacent generated_at sites in system.py and support.py.

2026-06-10 07:49:46 +02:00

..

app

fix(system): emit boot_time and generated_at as tz-aware UTC

2026-06-10 07:49:46 +02:00

tests

fix(system): emit boot_time and generated_at as tz-aware UTC

2026-06-10 07:49:46 +02:00

__init__.py

…