Parsing fails for events with a duration set to "DURATION:P" about caldav HOT 5 CLOSED

Issue related to vobject, not caldav. Closing issue here

from caldav.

We may consider abandoning vobject eventually.

Anyway, it's interesting to know if this is a breach of the standard or not. As I read https://tools.ietf.org/html/rfc5545#section-3.3.6 a single P without any trailing period information is invalid, hence it's not a bug in vobject.

There is always a question if one should create workarounds when software applications break the standard. I think the most proper would be:

1. try to fix this issue at the producer side, as the producer of the ical data is breaching the standard.
2. if the above fails, make a filter before feeding the data to the caldav library, i.e. a regexp replace s/^DURATION:P$/DURATION:P0S/

from caldav.

Thanks for the feedback on this.

I agree that 1. would be best, but that is not likely to happen anytime soon (the client is thunderbird/lightning).
Option 2 sounds doable, but that would have to done in caldav or am I wrong?

My current workaround is a fork of vobject where if this happens, I force a duration of 0s and all is fine.
Though of course I would very much prefer not to do it that way :-)

from caldav.

Thunderbird Lightning is an open source product, isn't it? Report the bug upstream, and perhaps it will be fixed.

I assume you have some interface code between Thunderbird and the python caldav library, that's where I would have put the workaround.

from caldav.

Sure, my point was that it would take a very long time before such a fix would land in my distro ;-)
Anyways, there is a caldav server (davical) involved. I will look into this more to be sure it is actually TB and not maybe davical, which does not conform to the RFC and have this reported wherever appropriate.

Thnx

from caldav.