Unable to Sync Anew Error Could Not Find UID

[agregson]

Hello,

I had to blow away an old org-caldav sync option and calendar as too many habits were placed in it and I was not able to remove without redoing it all. I have deleted the caldavInbox.org file, made a new calendar to sync with and org-caldav fails to sync with the following error:

org-caldav-generate-md5-for-org-entry: Could not find UID DS1-4db800f9-e487-4738-9e9a-f16c5d78683f.

There is no such UID in any of my org files.

Is there a way to reset org-caldav to not look for missing UID? Furthermore, this does not look like any UID format in my org files.

thanks for any help. Had to export to ics files for now.

[jackkamm]

The org-caldav sync state for each calendar is saved in ~/.emacs.d/org-caldav-<CALENDAR_ID>.el. You could try deleting the corresponding file and see if it fixes the problem.

org-caldav-delete-everything deletes the sync file as well as everything on the remote calendar.

We should also add functionality/documentation on how to just delete and start afresh on Org side, without deleting on CalDav side.

[agregson]

jackkamm ***@***.***> writes:

The org-caldav sync state for each calendar is saved in `~/.emacs.d/org-caldav-<CALENDAR_ID>.el`. You could try deleting the corresponding file and see if it fixes the problem. `org-caldav-delete-everything` deletes the sync file as well as everything on the remote calendar. We should also add functionality/documentation on how to just delete and start afresh on Org side, without deleting on CalDav side.

Thank you very much for your reply. I have done the `org-caldav-delete-everything` several times. I did also remove any mention of previously `~/.emacs.d/org-caldav-...el` files. I just did rerun this and confirm that I am receiving the exact same error message. To me it does seem like I should just be able to delete a file that has logged this mysterious UID and be done with it, but I am not able to find such a file to delete! Thanks, Aric

[jackkamm]

Does the ID 4db800f9-e487-4738-9e9a-f16c5d78683f exist in your Org files? Also, does it contain a diary-style timestamp within?

Note that ox-icalender.el (which org-caldav uses) exports a separate event for each timestamp within an entry, and adds a prefix to the ID for the type of timestamp (DS for diary, DL for deadline, etc). Org-caldav strips out the prefix as this would be incompatible with 2-way sync. It sounds like it's failing to strip out the DS1- prefix in this case for some reason.

I'd recommend also trying to directly run the ox-icalendar exporter directly on the file to see how the ICS looks.

[agregson]

Thank you again for your help. Indeed, the ID w/o the leading DS1 was found in my org files. It is with the "Anniversaries" section of my agenda.org file. This is where I have put a series of diary type dates for birthday counters. Once I removed the ID, org-caldav-sync creates another ID for this same heading and then gets stuck on the new ID just as it did the original! Exporting to ics just that file works, but the file gives an error "Invalid column last_modified" Calling org-caldav-sync I receive the same error: org-caldav-generate-md5-for-org-entry: Could not find UID DS1-e1570da5-734b-4dfe-bc1a-86b5e878b88d. Thanks, Aric

[jackkamm]

I just pushed this commit so that org-caldav can recognize IDs from diary style timestamps:
875bebe
So at least it should stop crashing.

That said, you probably don't want to export this to caldav, unless maybe if you're doing 1-way sync. Otherwise the diary-style timestamp could accidentally be overwritten in Cal->Org (org-caldav doesn't know how to import diary timestamps). You may want to consider using org-export-exclude-tags or org-caldav-skip-conditions to exclude that entry.

The issue was probably caused by a recent patch I submitted to ox-icalendar.el to export of diary timestamps:
https://list.orgmode.org/[email protected]/
I will work on a patch to ox-icalendar.el to skip the diary timestamps from export.

[jackkamm]

Also, can you provide more details about this:

Exporting to ics just that file works, but the file gives an error
"Invalid column last_modified"

At what point does that error occur?

[agregson]

jackkamm ***@***.***> writes:

I just pushed this commit so that org-caldav can recognize IDs from diary style timestamps: 875bebe So at least it should stop crashing.

It does fix my crashing error and allows me to sync the calendar again! Thank you so very much!

That said, you probably don't want to export this to caldav, unless maybe if you're doing 1-way sync. Otherwise the diary-style timestamp could accidentally be overwritten in Cal->Org (org-caldav doesn't know how to import diary timestamps). You may want to consider using `org-export-exclude-tags` or `org-caldav-skip-conditions` to exclude that entry.

These are my birthdays and few other events that I move about. I do only a 1-way sync (now). I figured out how to make the calendar read only on the other end (phone) and I hope that will prevent any issues from occurring in my org files. The anniversary dates are exported literally, which is fine, as it just tells me there is a birthday that day, but does not calculate the age. I have double events on the receiving end, but I hope that going forward that will not be the case. I probably messed it up a bit with all the false starts.

The issue was probably caused by a recent patch I submitted to ox-icalendar.el to fix its export of diary timestamps: ***@***.***/ I will see if I can add an option upstream to to skip the diary timestamps from export.

That is great! Thanks again very much for you time and effort on caldav sync, Aric

[agregson]

jackkamm ***@***.***> writes:

Also, can you provide more details about this: > Exporting to ics just that file works, but the file gives an error > "Invalid column last_modified" At what point does that error occur?

I have been able to export to ics since that error. It did clear up BEFORE I implemented your fix to the DS issue. If I find the error again, I will track it down and let you know. Thanks, Aric