search

TailorDev / Watson

:watch: A wonderful CLI to track your time!
http://tailordev.github.io/Watson/
MIT License
2.41k stars 237 forks source link

Aggregate ignores current day #466

Open MiltenPlescott opened 2 years ago

MiltenPlescott commented 2 years ago

Problem

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

```bash foo@bar:~$ watson log -G Monday 28 March 2022 (03s) 6899a52 16:16 to 16:16 03s github [bugreport] foo@bar:~$ ```

watson aggregate

```bash 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:~$ ```

frames

```json [ [ 1648476984, 1648476987, "github", "6899a52c2b28447baf5bcc4c9b47105e", [ "bugreport" ], 1648476987 ] ] ```

MiltenPlescott commented 1 year ago

Same problem today - Monday 27th is not showing up in aggregate. Again the day after daylight saving time change.