timewarrior

timewarrior copied to clipboard

Amado Martinez on 2016-11-26T23:39:29Z says:

$ timew start myactivity daily
You cannot overlap intervals. Correct the start/end time, or specify the :adjust hint.

I found this issue using the taskwarrior hook with a Task that had a custom "daily" tag.

I wonder if there are other tag names that are not permitted.

Migrated metadata:

Created: 2016-11-26T23:39:29Z
Modified: 2017-05-21T17:17:56Z

Paul Beckingham on 2016-11-28T16:55:27Z says:

Good catch! The used of daily as a tag is interpreted as a 24-hour recurrence period, and sets the start time to now-24h, which may overlap. I cannot find a workaround so I'm raising the priority.

To answer your question, any tag that matches a date (tuesday, eom, easter ...) or recurrence period (daily, weekly, annual ...) is going to have the same problem.

Thomas Lauf on 2017-04-12T04:38:25Z says:

Some ideas come into my mind:

1. repetitions make no sense with TimeWarrior, add a new type to the lexer and ignore it here
2. move parsing into the command. Commands like tag, start, stop do not expect durations, track does
3. make parsing more context aware. Terms like day, month, etc should require an amount specifier (2 days, 1 month, ...)

Paul Beckingham on 2017-05-21T17:17:45Z says:

I agree Thomas, I would prefer #3, which we can implement using the rat parser. Moving to backlog for now.

Just got bitten by this bug!

I suddenly got the You cannot overlap intervals. Correct the start/end time, or specify the :adjust hint. error and couldn't get the Taskwarrior tasks to hook into the Timewarrior any longer (or so it seemed).

This had me baffled er... for a time, since when looking into the Taskwarrior's task information, everything seemed normal.... Timewarrior reports or raw files, normal... systems's date and time, normal...

I made a backup of my Timewarrior database and did some tests, noticing that some of my tasks got recorded exactly 24 hours in the past. And that eventually brought me here.

Two suggestions:

• consider stating that there are reserved tag names in Taskwarrior (!) and Timewarrior documentation until this is mended (and what the consequences might be if one uses them anyway)
• if possible, make the You cannot overlap intervals. Correct the start/end time, or specify the :adjust hint. error more verbose by default (which time is one trying to record, which time does it conflict, which @id).

Perhaps debugging would have helped me here, but it wasn't my first hunch to resort to it just yet.

Anyway, thanks for working on this software. My first impressions after a couple of days is that the UI seems simple enough if one wants it to be and complex enough to accomplish practically any workflow, which to me is a sign of a very good software design. Taskwarrior and Timewarrior are just a joy to use.