Closed ecbftw closed 6 years ago
As I dig deeper into this, I'm focusing on this bit:
ValueError: RRULE UNTIL values must be specified in UTC when DTSTART is timezone-aware
The RRULE in the file (with some context) is:
DTSTART;TZID=America/Los_Angeles:20170428T140000
X-APPLE-TRAVEL-ADVISORY-BEHAVIOR:AUTOMATIC
CREATED:20170409T211157Z
RRULE:FREQ=MONTHLY;INTERVAL=1;UNTIL=20171125T075959Z;BYDAY=-1FR
Isn't 20171125T075959Z already in UTC time with that trailing Z
?
Ok, so now I see https://github.com/dateutil/dateutil/issues/620 talking about this, but I still don't know the best work-around...
More info in https://github.com/dateutil/dateutil/issues/652
Is this a bug in Radicale that needs to be addressed?
No, it's a bug in VObject: https://github.com/eventable/vobject/issues/112
You can either patch VObject (https://github.com/eventable/vobject/pull/111) or downgrade dateutil to an older version, that doesn't trigger the bug in VObject.
This is a duplicate of #764.
Is this a one-time issue with the export/import process, or will this issue crop up with new events created by the same CalDAV clients I have been using all along?
It's not a one-time issue.
Isn't 20171125T075959Z already in UTC time with that trailing
Z
?
Yes.
Ok, thanks much for clearing that up for me.
I tried patching VObject by changing that one key line in the (eventable/vobject#111) patch from:
ignoretz=isinstance(dtstart, datetime.date))
to:
ignoretz=(isinstance(dtstart, datetime.date) and not isinstance(dtstart, datetime.datetime)))
and it seems to have fixed the issue for now. (At least, it isn't blowing up on those files now.)
Same issue, @ecbftw's fix worked for me as well. Thanks
Fixed by 5cd43acb3c0391088f8f9fa52639c065fbc44f48
I'm attempting to upgrade from Radicale 1.1.x to 2.1.8. I followed the migration steps, exporting from the 1.1 version to a new database, and then I ran the new version with the
--verify-storage
command. Most of my ~1400 calendar entries verify fine, but about 15 of them fail to verify, all with the same error message. Here is the exception for one of them:Many of the calendar entries I don't care about, but some I do, since they were recently created. I'm attaching the ics file that caused the above exception. 16EC2639-ECD4-41DC-A999-A2BEDF055D8F.ics.txt
My questions are: