Start, end, duration time printed in CLI by taskwarrior-timewarrior python hook are incorrect.

[poetaman]

As pointed in the comment GothenburgBitFactory/taskwarrior#2514 (comment), the taskwarrior-timewarrior python hook prints incorrect start/end/duration times for some >>task commands. The example is described in the comment at GothenburgBitFactory/taskwarrior#2514 (comment) of taskwarrior's ticket: GothenburgBitFactory/taskwarrior#2514. Here's the minimal & edited quote from my comment that invites this ticket.

While the problem of GothenburgBitFactory/taskwarrior#2514 fixed, the information printed in stdout is still incorrect. Check the times printed under "Tracking", and "Recorded" to stdout in teal blue color in screenshot below. The "Started", "Ended" times, and resultant duration are all based on current_timestamp.

[tbabej]

Some coarse implementation hints are here and here

[tbabej]

@reportaman FYI, perhaps this currently open PR already partially addresses this issue: GothenburgBitFactory/timewarrior#329

[lauft]

FYI: GothenburgBitFactory/timewarrior#329 has been migrated to #5