Todoist Integration is broken #606

Closed
opened 2020-07-05 15:12:06 +00:00 by neoromantique · 19 comments

I have tried to set up Todoist migration but it's failing with a 500

2020-07-05T15:10:00.271834513Z: ERROR ? handler/Migrate 149 parsing time "2026-06-11T07:00:00": extra text: T07:00:00
2020-07-05T15:10:00.271926707Z: WEB ? 5.20.15.61 POST 500 /api/v1/migration/todoist/migrate 1.641519821s - Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

I have tried to set up Todoist migration but it's failing with a 500 > 2020-07-05T15:10:00.271834513Z: ERROR ? handler/Migrate 149 parsing time "2026-06-11T07:00:00": extra text: T07:00:00 > 2020-07-05T15:10:00.271926707Z: WEB ? 5.20.15.61 POST 500 /api/v1/migration/todoist/migrate 1.641519821s - Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Owner

I've just checked locally and could not reproduce the issue. Could you enable debug logs (set the log level to debug) and try migrating again to see if we can get more information about this?

I've just checked locally and could not reproduce the issue. Could you enable debug logs (set the log level to `debug`) and try migrating again to see if we can get more information about this?
Owner

Debug logs: https://pastebin.com/BheDjM7P
(from matrix)

Debug logs: https://pastebin.com/BheDjM7P (from matrix)
Owner

So it seems like todoist reminders use a different date formate than due dates but use the same data structure: https://developer.todoist.com/sync/v8/#reminders

I've pushed a fix to parse that in ec3fa9300b, please test with a new release once its ready (in about 40min).

So it seems like todoist reminders use a different date formate than due dates but use the same data structure: https://developer.todoist.com/sync/v8/#reminders I've pushed a fix to parse that in https://kolaente.dev/vikunja/api/commit/ec3fa9300b7147a2f010a4666c1caad53f733927, please test with a new release once its ready (in about 40min).
Owner

New fix: 78791f31a4

It seems like I've modified the wrong part of the date parser code, my bad.

As with the last one, a new release should be ready in about 40min, please test again once that's ready.

New fix: https://kolaente.dev/vikunja/api/commit/78791f31a41990b9b391b93a57b609c455969265 It seems like I've modified the wrong part of the date parser code, my bad. As with the last one, a new release should be ready in about 40min, please test again once that's ready.
Author
https://pastebin.com/wAnWWJG3
Owner

What DB are you using? Is it properly set up to use utf-8?

What DB are you using? Is it properly set up to use utf-8?
Author

What DB are you using? Is it properly set up to use utf-8?

I use mysql

vikunja_db:
image: mariadb:10

> What DB are you using? Is it properly set up to use utf-8? I use mysql > vikunja_db: > image: mariadb:10
Owner

Does it work if you migrate your db to utf-8: https://dba.stackexchange.com/a/104866 ?

Does it work if you migrate your db to utf-8: https://dba.stackexchange.com/a/104866 ?
Owner

There is now also an article in the docs which explains utf-8 conversion in more detail: https://vikunja.io/docs/utf-8-settings/

There is now also an article in the docs which explains utf-8 conversion in more detail: https://vikunja.io/docs/utf-8-settings/
Owner

It seems like my string splitting was not non-ascii-aware. #607 fixes that.

It seems like my string splitting was not non-ascii-aware. #607 fixes that.
Owner

Since it seems to work with #607 I'm going to close this issue, feel free to reopen if it persists.

Since it seems to work with #607 I'm going to close this issue, feel free to reopen if it persists.

I am getting the same errors about migrating data that were previously being gotten. Here is a link to the logs: https://pastebin.com/8G05yFF2

I am running the debian package for the backend, and have tried both vikunja_0.16.0+17-ef0035d4bd_amd64.deb and vikunja_0.16.0_amd64.deb, with both giving the same error.

I am getting the same errors about migrating data that were previously being gotten. Here is a link to the logs: https://pastebin.com/8G05yFF2 I am running the debian package for the backend, and have tried both vikunja_0.16.0+17-ef0035d4bd_amd64.deb and vikunja_0.16.0_amd64.deb, with both giving the same error.
Owner

@monkeynaleo What's happening in the debug logs?

@monkeynaleo What's happening in the debug logs?

I enabled DEBUG logging, and here is the log files. Same error as before.

I enabled DEBUG logging, and here is the log files. Same error as before.
Owner

@monkeynaleo This might be caused by due dates with times, do you have any of those?

@monkeynaleo This might be caused by due dates with times, do you have any of those?
konrad reopened this issue 2021-02-04 19:55:41 +00:00

Yes, I do have due dates with times.

Yes, I do have due dates with times.
Owner

I see, I'll test a fix.

I see, I'll test a fix.
Owner

Should be fixed with 490ba2ea50 - please check with a new release once its ready (Should take about 30-45min). Feel free to reopen if the issue is still not fixed.

Should be fixed with https://kolaente.dev/vikunja/api/commit/490ba2ea50f950c26dba02cbf3f37bbc1ade0b34 - please check with a new release once its ready ([Should take about 30-45min](https://drone.kolaente.de/vikunja/api/2706)). Feel free to reopen if the issue is still not fixed.

This problem appears to be fixed for me!

This problem appears to be fixed for me!
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/vikunja#606
No description provided.