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

Google calendar crashes with start/end date set #657

Closed
vestingz opened this Issue Aug 2, 2017 · 12 comments

Comments

Projects
None yet
3 participants
@vestingz

vestingz commented Aug 2, 2017

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:

status_path = "~/.vdirsyncer/status/"

[storage calendar_remote]
type = "google_calendar"
read_only = "true"
token_file = "~/.vdirsyncer/token"
client_id = "<SOMETHING>.apps.googleusercontent.com"
client_secret = "<SOMETHING>"
start_date = "datetime.now() - timedelta(days=10)"
end_date = "datetime.now() + timedelta(days=100)"

[storage calendar_khal_loc]
type = "filesystem"
path = "~/.calendars/calendar_khal/"
fileext = ".ics"

[pair calendar_khal]
a = "calendar_khal_loc"
b = "calendar_remote"
collections = ["from a", "from b"]
partial_sync = "ignore"
conflict_resolution = "b wins"
metadata = ["displayname"]

and the error log:
out0.txt

Edit: I did some more testing and it seems that deleting everything in ~/.vdirsyncer/status/ helps.

@untitaker

This comment has been minimized.

Member

untitaker commented Aug 2, 2017

Edit: I did some more testing and it seems that deleting everything in ~/.vdirsyncer/status/ helps.

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.

@vestingz

This comment has been minimized.

vestingz commented Aug 2, 2017

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?

@untitaker untitaker reopened this Aug 2, 2017

@untitaker

This comment has been minimized.

Member

untitaker commented Aug 2, 2017

The .items file would be useful (in addition to the debug logs)

@vestingz

This comment has been minimized.

vestingz commented Aug 3, 2017

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).

@untitaker

This comment has been minimized.

Member

untitaker commented Aug 5, 2017

@vestingz I can't decrypt the email you sent me. It appears to be encrypted with the wrong public key.

untitaker added a commit that referenced this issue Aug 12, 2017

@untitaker

This comment has been minimized.

Member

untitaker commented Aug 12, 2017

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?

@vestingz

This comment has been minimized.

vestingz commented Aug 14, 2017

Yes, removing the timeranger parameters helps indeed. thank you :)
This, however, bloats the calendar files as the calendar goes back to 2011..

@vestingz vestingz closed this Aug 14, 2017

@untitaker

This comment has been minimized.

Member

untitaker commented Aug 15, 2017

I don't think this is ready to close yet... needs further investigation.

@untitaker untitaker reopened this Aug 15, 2017

@untitaker

This comment has been minimized.

Member

untitaker commented Aug 15, 2017

I can even reproduce this with my own calendar

@untitaker untitaker changed the title from "Unknown error" on sync with Google Calendar to Google calendar crashes with start/end date set Aug 15, 2017

@untitaker untitaker closed this in 35ffdd6 Aug 15, 2017

@stettberger

This comment has been minimized.

stettberger commented Sep 5, 2017

Thank you for fixing this bug. It also bit me.

@vestingz

This comment has been minimized.

vestingz commented Sep 5, 2017

Thanks for the fix, it works now. However I'm still getting errors. Here an excerpt from the error log:

debug: Skipping '/caldav/v2/<DOMAIN>_je1j4hgur5pfm73jkkscocsje4@group.calendar.google.com/events/29vu9tquncs21fh75b9b08icq4_R20150521T120000@google.com.ics', properties are missing.
debug:   File "/usr/lib/python3.6/site-packages/vdirsyncer/cli/tasks.py", line 69, in sync_collection
debug:     partial_sync=pair.partial_sync
debug:   File "/usr/lib/python3.6/site-packages/vdirsyncer/sync.py", line 561, in sync
debug:     b_nonempty = b_info.prepare_new_status()
debug:   File "/usr/lib/python3.6/site-packages/vdirsyncer/sync.py", line 484, in prepare_new_status
debug:     if prefetch else ()):
debug:   File "/usr/lib/python3.6/site-packages/vdirsyncer/storage/dav.py", line 500, in get_multi

[...]

debug: Skipping '/caldav/v2/<DOMAIN>_9ps4c8man8las4gb645ap7j34o@group.calendar.google.com/events/29vu9tquncs21fh75b9b08icq4@google.com.ics', properties are missing.
debug:   File "/usr/lib/python3.6/site-packages/vdirsyncer/cli/tasks.py", line 69, in sync_collection
debug:     partial_sync=pair.partial_sync
debug:   File "/usr/lib/python3.6/site-packages/vdirsyncer/sync.py", line 561, in sync
debug:     b_nonempty = b_info.prepare_new_status()
debug:   File "/usr/lib/python3.6/site-packages/vdirsyncer/sync.py", line 484, in prepare_new_status
debug:     if prefetch else ()):
debug:   File "/usr/lib/python3.6/site-packages/vdirsyncer/storage/dav.py", line 500, in get_multi
debug:     raise exceptions.NotFoundError(href)
[...]```
@untitaker

This comment has been minimized.

Member

untitaker commented Sep 8, 2017

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment