Closed taskwarrior closed 6 years ago
Migrated metadata:
Created: 2011-03-16T12:56:58Z
Modified: 2014-02-09T02:06:35Z
Aikido Guy on 2011-03-16T12:58:11Z says:
$ task diagnostic task 1.9.4 Platform: Cygwin Compiler Version: 4.3.4 20090804 (release) 1 Caps: +stdc +stdc_hosted +200112 +c1 +i4 +l4 +vp4 Libraries Readline: n/a Lua: n/a Build Features Built: Mar 5 2011 00:03:17 Caps: +pthreads +srandom +random -uuid Configuration File: /blah/.taskrc (found), 1984 bytes, mode 100644 Data: /blah/Tasks (found), dir, mode 40777 Locking: Enabled Regex: Disabled External Utilities scp: found rsync: 3.0.7 curl: 7.20.1 Tests UUID gen: 1000 unique UUIDs generated. $TERM: xterm (160x66)
Cory Donnelly on 2011-03-16T14:33:25Z says:
I can't recreate this under 1.9.4 on OSX. Were you not prompted before making changes to the two other tasks? Were the changes made without your authorization?
~/git/194final/src cory$ ./task 2,1,3 due:Today Task 1 "One" * due will be set to '3/16/2011'. Proceed with change? (yes/no/all/quit) yes Task 2 "Testing" * due will be set to '3/16/2011'. Proceed with change? (yes/no/all/quit) yes Task 3 "Three" * due will be set to '3/16/2011'. Proceed with change? (yes/no/all/quit) yes Modified 3 tasks.
Aikido Guy on 2011-03-16T15:18:35Z says:
I received 1 confirmation message and I only typed 'yes' once and the message from Task said that 1 task was modified. However, all 3 tasks were updated as expected... simply the messages were not displayed.
Federico Hernandez on 2011-03-16T17:36:32Z says:
I can't reacreate this neither: on OS X, ubuntu nor cygwin with default shell/terminal nor with mintty (default settings in .taskrc)
How does your .taskrc look like? What values do you have in .taskrc that are different from the default ones. Check the output of task show, please.
Cory Donnelly on 2011-03-17T10:49:12Z says:
We can't seem to reproduce your issue. A copy of your data and .taskrc file that exhibits this problem would be really helpful. If you get into a state where you can reproduce this problem again (or if you're motivated enough to (at)task undo@ yourself back to a place where this reoccurs), please attach the relevant files to this issue. To sanitize your data, download and use the data anonymizer [[Task-anon]]. Thanks!
Aikido Guy on 2011-03-20T17:12:16Z says:
I would love to undo to a point in which I had the original problem... but I can't seem to undo. Looks like a loop to me... attached is my current anon output.
To be clear, I was performing the following action on cygwin:
task undo
Cory Donnelly on 2011-03-27T13:03:30Z says:
Thanks, Aikido Guy -- if you experience the issue again, please let us know.
Aikido Guy on 2011-08-27T18:03:46Z says:
I have a problem with a 'duration' and 'undo' on cygwin 1.9.4 that seem related to my comments above.
task add "some task; and a bit more description" project:Career due:now recur:1month Created task 64. Configuration override curses=off Configuration override defaultwidth=58 The duration '-' was not recognized.
I didn't know why '-' was not recognized since I didn't type it at the command line and I had forgotten to add my tag '+HH'. So, I wanted to undo my change and then add the recurring task with the tag included.
$ task undo The last modification was made 8/27/2011 Prior Values Current Values description some task; and a bit more description due 2011/09/26_13:35 entry 2011/08/27_13:35 imask 1 parent fc01eaac-5c12-03c1-d4d0-1f17951c46e4 project Career recur 1month status pending uuid e237205e-e5af-18d1-4b2f-ab3e64664392 The undo command is not reversible. Are you sure you want to revert to the previous state? (y/n) y Task removed. Configuration override curses=off Configuration override defaultwidth=58 [Shadow file 'taskShadow.txt' updated.] $ task undo The last modification was made 8/27/2011 Prior Values Current Values description some task; and a bit more description due 2011/08/27_13:35 entry 2011/08/27_13:35 imask 0 parent fc01eaac-5c12-03c1-d4d0-1f17951c46e4 project Career recur 1month status pending uuid 2e5090ce-ce0c-1cee-0be1-bf944a180fc3 The undo command is not reversible. Are you sure you want to revert to the previous state? (y/n) y Task removed. Configuration override curses=off Configuration override defaultwidth=58 [Shadow file 'taskShadow.txt' updated.] $ task undo The last modification was made 8/27/2011 Prior Values Current Values description some task; and a bit more description some task; and a bit more description due 2011/08/27_13:35 2011/08/27_13:35 entry 2011/08/27_13:35 2011/08/27_13:35 project Career Career recur 1month 1month status recurring recurring uuid fc01eaac-5c12-03c1-d4d0-1f17951c46e4 fc01eaac-5c12-03c1-d4d0-1f17951c46e4 mask -- The undo command is not reversible. Are you sure you want to revert to the previous state? (y/n) y Modified task reverted. Configuration override curses=off Configuration override defaultwidth=58 [Shadow file 'taskShadow.txt' updated.] $ task undo The last modification was made 8/27/2011 Prior Values Current Values description some task; and a bit more description due 2011/09/26_13:35 entry 2011/08/27_13:35 imask 1 parent fc01eaac-5c12-03c1-d4d0-1f17951c46e4 project Career recur 1month status pending uuid c027e0d7-3479-f9aa-1a7c-f797a6daf1fb The undo command is not reversible. Are you sure you want to revert to the previous state? (y/n) y Task removed. Configuration override curses=off Configuration override defaultwidth=58 [Shadow file 'taskShadow.txt' updated.] $ task undo The last modification was made 8/27/2011 Prior Values Current Values description some task; and a bit more description due 2011/08/27_13:35 entry 2011/08/27_13:35 imask 0 parent fc01eaac-5c12-03c1-d4d0-1f17951c46e4 project Career recur 1month status pending uuid 54bdaed6-936f-5b21-b80d-b5fd73d60845 The undo command is not reversible. Are you sure you want to revert to the previous state? (y/n) y Task removed. Configuration override curses=off Configuration override defaultwidth=58 [Shadow file 'taskShadow.txt' updated.] $ task all "some task" ID Project Pri Due Completed Active Age Description 64 Career 2011/08/27_13:35 1 min some task; and a bit more description 1 task
At this point I got tired of trying to undo; so I went to the text files and deleted the relevant lines.
Then I successfully added my task
$ task add "some task; and a bit more description" project:Career due:2011/08/27_14:00 recur:1month +HH Created task 64. Configuration override curses=off Configuration override defaultwidth=58 [Shadow file 'taskShadow.txt' updated
Notice that I changed "due:now" to "due:2011/08/27_14:00", which was about 20min. into the future. Maybe the duration error I received was because by the time 'now' was processed, it was in the past? Just a guess... not sure about internal workings of task warrior. Still a wonderful program though :)
Paul Beckingham on 2011-10-16T03:51:37Z says:
I discovered something. In the original bug description:
$ task 20,37,36 due:Today
Suppose that 36 and 37 were already due:today. That would explain the 'Modified 1 task'. Could this possibly be the case?
Aikido Guy on 2011-10-17T21:33:15Z says:
Yes, that could have been the case! However, I can't imagine that I would have tried to change the due date if it was already today... but who knows, that was back when I was a real newbie and now I don't make mistakes! err.. well... Anyway, I'd suggest that if what you've found is true, then simply adding a message to say 2 tasks already have a due date of today would be sufficient to solve the problem. However, when exactly would 'today' be? If 36,37 were due today at noon, what would performing the 'due:Today' action do? Change them to midnight? In other words, if '20' was due yesterday and it was ok to change it to 'due:Today' then at what time would '20' now be due?
Paul Beckingham on 2011-10-28T02:44:50Z says:
Anyway, I'd suggest that if what you've found is true, then simply adding a message to say 2 tasks already have a due date of today would be sufficient to solve the problem. However, when exactly would 'today' be? If 36,37 were due today at noon, what would performing the 'due:Today' action do? Change them to midnight? In other words, if '20' was due yesterday and it was ok to change it to 'due:Today' then at what time would '20' now be due?
Midnight, I believe.
Paul Beckingham on 2012-01-30T05:17:42Z says:
I believe this has been resolved.
Aikido Guy on 2011-03-16T12:56:58Z says:
I would have expected one for Task 37 and another for Task 36. I would also expect that 3 tasks would be modified, not 1.