The function org-caldav-create-time-range can be called from org-caldav-update-events-in-org with an incorrect number of arguments. The original code passes (butlast eventdata 3) as arguments. However, since org-caldav-create-time-range expects exactly four arguments, this will fail unless eventdata has exactly seven elements.
The fix replaces (butlast eventdata 3) with (seq-take eventdata 4).
I managed to trigger the failure once when I added a "note" to a Google calendar event ("DESCRIPTION:" in caldav).
Edit: On second thoughts, this bug might only be necessary if you have have added CLASS (pull request #161). Adding the fix to the main branch would still remove the latent bug.
The function
org-caldav-create-time-rangecan be called fromorg-caldav-update-events-in-orgwith an incorrect number of arguments. The original code passes(butlast eventdata 3)as arguments. However, sinceorg-caldav-create-time-rangeexpects exactly four arguments, this will fail unlesseventdatahas exactly seven elements.The fix replaces
(butlast eventdata 3)with(seq-take eventdata 4).I managed to trigger the failure once when I added a "note" to a Google calendar event ("DESCRIPTION:" in caldav).
Edit: On second thoughts, this bug might only be necessary if you have have added CLASS (pull request #161). Adding the fix to the main branch would still remove the latent bug.