Closed FrnchFrgg closed 10 months ago
I think this bug was fixed in master branch yesterday. Please check.
I found the same problem when writing up tests in #354, so the fix was piggybacked there.
Right, HomeAssistant ... dependent on how you are running it, it may be really difficult to check how it works with the master branch. I will make a new minor release Real Soon Now. Possibly tomorrow.
I think this issue has been fixed and will close the issue. Please correct me if I'm wrong.
Yes I can confirm this issue is fixed in latest caldav
.
Even though when generating the data all property names are uppercased, this is not done before iterating the properties which means that all possible cases will generate duplicates. In particular using any other case in the
save_todo
call will fail since that will be considered a duplicate of the STATUS property inserted as a default bycaldav
itself.Note that the error is probably hidden when using more forgiving CALDAV servers than mine: reading the traceback below it seems that the error is indeed raised the
caldav
library but that it only validates the event onPUT
failure.I use
radicale
which AFAICT refuses the VTODO because it also validates it withvobject
(since I get the exact same error in the radicale logs)