Open jkaiser-ioki opened 4 months ago
I could swear I replied to this, I'm sorry.
I wasn't able to reproduce this, using the same commands you used.
Can you confirm you're not using sync
? Are there any other processes running in the background (cron task, another terminal, etc.) that might be applying recurrence at the same time?
I never set up or enabled sync
as far as I know, so if it isn't turned on automatically somehow, I am pretty sure it is not running.
The only automated thing I can think of is my status bar (i3status-rust), which has two configured blcoks that each query task
every 60 seconds. From my understanding, the commands are configured to not change the task IDs, i.e. if found this in the underlying implementation:
Command::new("task")
.args(["rc.gc=off", filter, "count"])
.output()
I assume the rc.gc=off
is the reason why the IDs do not change (which is good since I don't want the IDs to jump between one command manually viewing the task list and a another modifying one by ID), but maybe recurrence updates are still triggered despite that flag, and by some chance the two blocks fire so close to each other that that causes duplicates?
I suspect that's the issue, or at least part of it. Try adding rc.recurrence.limit=0
to that command line?
hmm, that code is not from me so I cannot really test your suggestion as such...
I'll disable one of the blocks for a while to see if the issue goes away, and if that is the case, I will open a ticket with the status bar application to consider incorporating your change. Is there any documentation reg. those rc.*
options and their behaviour I could point their devs to? That might simplify the process of determining if that extra flag is the one that is needed, if it should always be included or whether it might be exposed through some form of configuration on their end.
Actually juts rc.recurrence=off
should do -- it's in the taskrc(5)
manpage.
All my recurrences create duplicate new instances when the next instance is required. The issued appeared when I migrated to 3.0.0, and I assumed that it was an import problem, but the same happens on freshly created recurrences. The following details are for the recurrence I just added:
Expectation: Creation of the recurrence template (ID 143), plus one actual child instance (ID 144).
Actual: the expected, plus a duplicate of ID 144 , with ID 145
Relevant observations
Virtual tag
LATEST
Output of the
task diag
commandMy Configuration
(just in case that we happens is due to some misconfiguration and not an actual TW bug)