bugwarrior runs (using taskw) are putting blocks of NUL bytes in my completed.data about taskw

[pawamoy]

Possibly due to concurrent accesses by taskwarrior. See my comment here for a workaround. People (including me) have had this corruption issue without even using bugwarrior so I'm not sure about bugwarrior's responsibility here.

[djmitche]

As you can see from the comment above, there was no access by taskwarrior at the time of the corruption.

[coddingtonbear]

Are you certain you do not have an unwrapped periodic (cron) task running, maybe, 'sync'? As @pawamoy said, I've never seen that happen in situations other than during concurrent accesses.

[djmitche]

It's been a long time since I've seen this, so I can't be sure. task sync does run at */10 (in a cron that uses /usr/bin/task and thus misses the wrapper), but what else would have run at that time? All bugwarrior and cli use of task is through the wrapper. Anyway, we can close this since it has not recurred.