-
Notifications
You must be signed in to change notification settings - Fork 50
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
Tasks with due:someday
(9999-12-30) break sync
#369
Comments
I am also facing this issue, which sometimes crashes the sync process (and However, I can still sync without any problems if I just wait a while. Furthermore, The error I faced, taken from the inthe.am activity log:
|
@kamalmarhubi are you on the development branch(2.6.0)? As they changed the date format in 2.6.0 along with some other major date and numeric items.
inthe.am runs a forked version of the taskd server, changes will have to be made to it to resolve the issue you are having. With just glancing over the release notes on 2.6.0 there are going to be other breaking changes related to dates, and numeric values with the version of server. You happen to just find the first one. I'll put in a PR in that repo to make the changes. Your best bet is to revert to the stable version of the client for now and your issue will be resolved. |
I am indeed. Good catch, and thanks for pointing that out. |
I believe this'll be fixed by #374 -- if any of you all want to try to pull that particular issue across the finish line, I've posted some notes to that issue so you can take advantage of my merge conflict resolutions. |
Repro:
The inthe.am tasks view stops updated, and this error appears in the logs:
The timestamp 253402146000 corresponds to
someday
aka 9999-12-30:The task syncs successfully from my local taskwarrior 2.6.0, so this might be something to do with the representation of this information in postgres?
The only workaround I've found is to delete task data in inthe.am, delete and purge the task, and then
task sync init
again.Full error including rc overrides
The text was updated successfully, but these errors were encountered: