Skip to content
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

[TW-1810] Completing a recurring task sometimes creates an empty entry in data and wipes some other entries #1831

Open
taskwarrior opened this issue Feb 14, 2018 · 14 comments
Labels
Milestone

Comments

@taskwarrior
Copy link

@taskwarrior taskwarrior commented Feb 14, 2018

Roy Zuo on 2016-06-01T23:52:42Z says:

It does not happen every time, but when it does, the result is messy.

It creates an empty entry "[]" in completed.data, and it deletes a lot of entries from pending.data. Please check the attachment for command outputs of the symptom.

I am not sure if this is directly associated my marking a recurring task as completed, but this is the second time I see it after upgrading to 2.5.1.

@taskwarrior taskwarrior added this to the Backlog milestone Feb 14, 2018
@taskwarrior
Copy link
Author

@taskwarrior taskwarrior commented Feb 14, 2018

Migrated metadata:

Created: 2016-06-01T23:52:42Z
Modified: 2016-08-09T01:24:34Z

Loading

@taskwarrior
Copy link
Author

@taskwarrior taskwarrior commented Feb 14, 2018

Paul Beckingham on 2016-06-02T00:02:37Z says:

Can we get some more details please: Hooks involved? Extensions? Sync? Dropbox? Server version? Mirakel? How many clients?

Loading

@taskwarrior
Copy link
Author

@taskwarrior taskwarrior commented Feb 14, 2018

Roy Zuo on 2016-06-02T00:12:06Z says:

My setting is pretty basic. Local machine without any hooks, extension or syncing.

I am actually thinking about setting up a task server right now. I have all the data I need to recover from backlog.data, but I do not know how.

Loading

@taskwarrior
Copy link
Author

@taskwarrior taskwarrior commented Feb 14, 2018

Roy Zuo on 2016-08-05T05:37:20Z says:

It happens again. This time it is not a recurring task.

Loading

@taskwarrior
Copy link
Author

@taskwarrior taskwarrior commented Feb 14, 2018

Roy Zuo on 2016-08-05T05:51:06Z says:

I notice the tasks are still in the file, but they could not be displayed when list command is issued. Could you have a look what is wrong with the formatting of the file?

Loading

@taskwarrior
Copy link
Author

@taskwarrior taskwarrior commented Feb 14, 2018

Paul Beckingham on 2016-08-05T11:02:30Z says:

Thanks for the data. Taking a look.

Loading

@taskwarrior
Copy link
Author

@taskwarrior taskwarrior commented Feb 14, 2018

Paul Beckingham on 2016-08-09T01:24:34Z says:

I have played with this sample data a lot, and cannot reproduce the problem, but I am leaving this issue open. I will try again.

Loading

@pbeckingham
Copy link
Member

@pbeckingham pbeckingham commented Feb 25, 2018

Loading

@ad-si
Copy link

@ad-si ad-si commented Jun 1, 2018

This is pretty awful. I guess it should have a higher priority!

Loading

@ad-si
Copy link

@ad-si ad-si commented Jun 3, 2018

Just had this issues again. Makes Taskwarrior completely unusable 😭

Loading

@pbeckingham
Copy link
Member

@pbeckingham pbeckingham commented Jun 3, 2018

Are you using hooks? Are you using some file sharing mechanism for syncing? Are you launching any task command out of cron.

Need more details, because this is not reproducible.

Loading

@ad-si
Copy link

@ad-si ad-si commented Jun 3, 2018

  • I'm using the https://taskwarrior.org/docs/timewarrior/taskwarrior.html hook
  • No file sharing
  • No cron
  • I show the number of open tasks in my cli prompt. (i.e. runs this everytime:
    task _get rc.context
    task +PENDING count
    task rc.report.active.columns=description rc.report.active.labels=d active 2> /dev/null |  sed '4q;d'

Loading

@ad-si
Copy link

@ad-si ad-si commented Jun 5, 2018

@pbeckingham I haven't bee using taskwarrior at all over the last few days, but it get's called with the commands described above every time my prompt renders.
Just this calls were enough to break it again just now.

Loading

@jcrben
Copy link
Member

@jcrben jcrben commented Jun 16, 2018

If you can provide reproducible steps in a repo that we could pull down, that would go a long way to helping this get fixed. Even better if you can do it in a plain vm. You can see above that Paul spent some time trying to reproduce this on 2016-08-09T01:24:34Z

Please provide task diagnostic output?

What's your taskrc look like?

I show the number of open tasks in my cli prompt. (i.e. runs this everytime:

What shell and version? How are you doing this - PROMPT_COMMAND or PS1?

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants