Archiving and deleting broken when task creation date is missing about pter HOT 7 CLOSED

Thanks for investigating! I'll see how to fix this

from pter.

Tested, seems to work fine, thank you!

from pter.

Strange, I can't reproduce it anymore... @vonshednob Can you?

from pter.

OK, figured it out!

abc xyz 123 due:2024-12-12 <- this kind of task will trigger the bug
2023-01-01 abc xyz 123 due:2024-12-12 <- this kind of task will NOT trigger the bug

Missing creation date seems to be the culprit. I have tasks with and without it.

from pter.

I cannot reproduce the issue, but I cannot archive tasks either 😅 so I'm fixing that bug at least.

I also see how the bug that you describe could be triggered, but I don't understand how pter can get into this type of situation. I'll investigate some more.

from pter.

Ah! I think I understand how this happened. Probably happened every 2nd time you try to archive a task; but the first time it doesn't actually archive it (because that was broken with an update to pytodotxt, I think).

The change is in how pter triggers the detection of a change in the task: task.parse(""), but with a more recent version(?) of pytodotxt parsing an empty string would not cause any change in the description, thus the task appears unchanged → problems.

Anyway, appears to be fixed for both deletion and archiving (not released yet, but the changes are in the codeberg repo).

from pter.

Probably happened every 2nd time you try to archive a task; but the first time it doesn't actually archive it

I think so, yes. Try to archive the first time -- nothing appears to happen. Try to do it a second time -- pter crashes.

but I don't understand how pter can get into this type of situation

I've migrated my todo.txt from another tool and some of my todos had missing creation dates. That may have been a factor.

Thanks for fixing it, I'll test the code soon.

from pter.