You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Monday 28th March is not showing up in aggregate, despite log working correctly. This problem happened for the first time after using watson for months, so I guess it's maybe related to the daylight saving time change that happened on Sunday?
Update (29th): the 28th started showing up in aggregate but 29th doesn't show up.
As a workaround you can use watson aggregate --from today --to today (where today is in YYYY-MM-DD)
Enviroment
Time zone: CEST
Windows 10 21H2
I was able to make a minimal reproducible example on WSL:
Ubuntu 20.04.3 LTS
Python 3.8.10
Watson, version 2.0.1
Logs
watson log
foo@bar:~$ watson log -G
Monday 28 March 2022 (03s)
6899a52 16:16 to 16:16 03s github [bugreport]
foo@bar:~$
watson aggregate
foo@bar:~$ watson aggregate -G
Mon 21 March 2022 - 00s
Tue 22 March 2022 - 00s
Wed 23 March 2022 - 00s
Thu 24 March 2022 - 00s
Fri 25 March 2022 - 00s
Sat 26 March 2022 - 00s
Sun 27 March 2022 - 00s
foo@bar:~$
Problem
Monday 28th March is not showing up in
aggregate
, despitelog
working correctly. This problem happened for the first time after using watson for months, so I guess it's maybe related to the daylight saving time change that happened on Sunday?Update (29th): the 28th started showing up in aggregate but 29th doesn't show up.
As a workaround you can use
watson aggregate --from today --to today
(where today is in YYYY-MM-DD)Enviroment
Time zone: CEST
Windows 10 21H2
I was able to make a minimal reproducible example on WSL:
Ubuntu 20.04.3 LTS
Python 3.8.10
Watson, version 2.0.1
Logs
watson log
watson aggregate
frames
The text was updated successfully, but these errors were encountered: