https://dagster.io/ logo
Powered by
#announcements
Title
# announcements
a

Auster Cid

03/25/2020, 3:05 PM
Hi again guys, I've got a small problem with the timestamps on dagit runs/logs
So I've set up a dagit instance using dagster-aws. Then I changed its timezone using 
dpkg-reconfigure tzdata
so it's using my local time (UTC-3). But now dagit shows runs in UTC-6 and execution logs in UTC.
Copy code
/opt/dagster$ timedatectl
                      Local time: Wed 2020-03-25 12:20:34 -03
                  Universal time: Wed 2020-03-25 15:20:34 UTC
                        RTC time: Wed 2020-03-25 15:20:34
                       Time zone: America/Sao_Paulo (-03, -0300)
       System clock synchronized: yes
systemd-timesyncd.service active: yes
                 RTC in local TZ: no
s

schrockn

03/25/2020, 3:15 PM
I believe @yuhan was looking at this. Will let her weigh in
y

yuhan

03/25/2020, 3:29 PM
I have a fix ready. Will let you know when it’s landed. Cc @sashank - bumping up for review
a

Auster Cid

03/25/2020, 3:44 PM
cool, thanks!
y

yuhan

03/25/2020, 7:38 PM
hi @Auster Cid this fix is merged to master. feel free to pull and try if it works.
👍 1
🙌 1
we found the issue was at the storage level — we didn’t persist the starttime and endtime of a run in correct timezone shift, which messed up the display in dagit’s run tab. the fix will only apply to the runs after this change. the historical runs will still have incorrect timezone conversion unfortunately. just to clarify, in dagit, now 
Runs
and 
Schedules
tabs show time info in your local time, while the raw event logs show time in UTC
Powered by