taskwarrior: wait:later or wait:someday break sync command
The use of wait:later or wait:someday break synchronisation with taskd servers.
-
What command(s) did you run? I have 2 devices, a computer running Arch Linux and a phone running Android 10. In the ArchLinux computer I ran
task add some task wait:latertask syncThen, in my Android phone I rantask sync(these were run in both Taswarrior for Android as well as Foreground) -
What did you expect to happen? I expected synchronisation to be successful.
-
What actually happened? I got the error
'253402128000' is not a valid date in the 'm/d/Y' format.. -
Paste the output of the
task diagcommand.
task 2.6.1 Platform: Linux
Compiler Version: 11.1.0 Caps: +stdc +stdc_hosted +LP64 +c8 +i32 +l64 +vp64 +time_t64 Compliance: C++17
Build Features CMake: 3.21.3 libuuid: libuuid + uuid_unparse_lower libgnutls: 3.7.2 Build type:
Configuration File: /home/pablo/.taskrc (found), 1985 bytes, mode 100644 Data: /home/pablo/.task (found), dir, mode 40755 Locking: Enabled GC: Enabled $EDITOR: nvim Server: tansanchez.net:53589 CA: /home/pablo/.task/ca.cert.pem, readable, 4001 bytes Certificate: /home/pablo/.task/pablo.cert.pem, readable, 3765 bytes Key: /home/pablo/.task/pablo.key.pem, readable, 24745 bytes Trust: strict Ciphers: NORMAL Creds: tansanchez/pablo/************************************
Hooks System: Enabled Location: /home/pablo/.task/hooks Active: on-modify.timewarrior (executable) Inactive:
Tests Terminal: 120x30 Dups: Scanned 173 tasks for duplicate UUIDs: No duplicates found Broken ref: Scanned 173 tasks for broken references: No broken references found
I though this error might have to do with the recent changes made to Taskwarrior in order to support 64 bit timestamps so I thought it might be the clients not handling that properly so, since Taskwarrior for Android is no longer in development, I decided to create an issue in the Foreground project. I got a suggestion there so I tried to remove the .data files and resync (prior copying the old ones) and I got the exact same error.
I agree with the response I got. It seems taskd accepts anything as a date but when it is delivered to the clients, it checks the timestamp and fails.
For the time being I have set the tasks that are causing the problem as wait:tomorrow but even after making that change, the synchronisation won’t happen. When I look at the data, the only place where I can find the problematic timestamp is in the undo.data. Is it possible to purge the undo.data just for the sake of getting the server to sync properly while this bug is being fixed.
Thaks in advance for your help.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 2
- Comments: 16 (1 by maintainers)
Very disappointing. This bit me. 😦
Sorry for the necro but should consider removing
somedayas a valid option if it bricks syncing.For anyone coming after me, here is a quick solution:
If you have one computer that has all the tasks and you are running your own sync server: move
tx.dataout of the folder (it will be your user folder inside of the org folder) / rename to something besidestx.datathen runtask sync initto entirely start over after you have modified the task that has the due date ofsomeday.