Google calendar crashes with start/end date set #657
Comments
Ok, since you deleted the data I can't help figure out what the issue was, but it appears that there's a bug in vdirsyncer... somewhere. |
No problem, I can upload those files somewhere, as the bug reproducibly appears after running vdirsyncer the first on an empty status directory. It then creates those files again and fails with seemingly the same error the next time I run it. Which files exactly would be helpful? |
The .items file would be useful (in addition to the debug logs) |
I will send you the .items file to your personal email, as they contain information I'd rather not share publicly. Please also find the debug log in the original post (out.txt). |
@vestingz I can't decrypt the email you sent me. It appears to be encrypted with the wrong public key. |
Hmm, the status file you sent me didn't help. I also don't understand how you get the error you're experiencing, regardless of the server's response it should be impossible to get into this state. Could you try to remove your timerange parameters? |
Yes, removing the timeranger parameters helps indeed. thank you :) |
I don't think this is ready to close yet... needs further investigation. |
I can even reproduce this with my own calendar |
Thank you for fixing this bug. It also bit me. |
Thanks for the fix, it works now. However I'm still getting errors. Here an excerpt from the error log:
|
@vestingz please file a new issue since this appears to be a separate bug, and also include the full debug output since i can't work with this excerpt. |
I am using vdirsyncer v0.16.0, Python 3.6.2 on Arch 4.12.3-1. I set up a pair for syncing between my local calendar and the calendars of my organization hosted by Google. Discovering the collections (vdirsyncer discover) works well, as did the sync, at least for the first time. Since then I have been trying to sync this pair without any success; vdirsyncer returns "Unknown error..." (see debugfile).
Here is my (sanitized) config:
and the error log:
out0.txt
Edit: I did some more testing and it seems that deleting everything in ~/.vdirsyncer/status/ helps.
The text was updated successfully, but these errors were encountered: