New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TI-75] The :fill hint not properly detecting the last interval #79

Closed
taskwarrior opened this Issue Feb 11, 2018 · 4 comments

Comments

Projects
None yet
1 participant
@taskwarrior

taskwarrior commented Feb 11, 2018

Tomas Babej on 2017-04-20T09:17:22Z says:

Look at the following scenario:

$ timew track 20170419T130000 - 20170420T040000 tag1
Recorded tag1
  Started 2017-04-19T13:00:00
  Ended           20T04:00:00
  Total              15:00:00
$ timew track 20170420T040000 - 20170420T101500 tag2
Recorded tag2
  Started 2017-04-20T04:00:00
  Ended              10:15:00
  Total               6:15:00
$ timew start tag3
Tracking tag3
  Started 2017-04-20T11:13:47
  Current                  47
  Total               0:00:00
$ timew summary :ids

Wk  Date       Day ID Tags    Start      End    Time    Total
W16 2017-04-20 Thu @3 tag1  0:00:00  4:00:00 4:00:00
                   @2 tag2  4:00:00 10:15:00 6:15:00
                   @1 tag3 11:13:47        - 0:00:38 10:15:38
                                                             
                                                     10:15:38

$ timew track :fill 20170420T101500 - 20170420T105000 tag4
Backfilled to 2017-04-20T04:00:00
Filled to 2017-04-20T11:13:47
You cannot overlap intervals. Correct the start/end time, or specify the :adjust hint.

The last command got backfilled back to the end of interval @3, instead of interval @2.

@taskwarrior taskwarrior added this to the 1.1.0 milestone Feb 11, 2018

@taskwarrior

This comment has been minimized.

taskwarrior commented Feb 11, 2018

Migrated metadata:

Created: 2017-04-20T09:17:22Z
Modified: 2017-12-02T12:27:49Z
@taskwarrior

This comment has been minimized.

taskwarrior commented Feb 11, 2018

Thomas Lauf on 2017-04-28T15:18:48Z says:

I currently do not understand what the problem is exactly. Can you supply the expected application output? Thank you.

@taskwarrior

This comment has been minimized.

taskwarrior commented Feb 11, 2018

Tomas Babej on 2017-04-28T21:01:06Z says:

The new interval got backfilled to 04:00:00 while it should have been backfilled to 10:15:00.

In other words, backfilling over an existing interval and then complaining that intervals cannot overlap is not smart from timewarrior.

@taskwarrior

This comment has been minimized.

taskwarrior commented Feb 11, 2018

Thomas Lauf on 2017-12-01T22:25:25Z says:

The bug occurs when a border of the given interval matches exactly with an existing interval border. I could fix it by softening the comparison from < to <=.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment