Closed zakkak closed 5 years ago
That's not an even it's trying to delete, but rather the calendar itself. Be lock such operations in etesync-dav, which is why it's failing. Any idea why the mac would try to do that? An easy way to get things to work again is to remove your calendar account from the mac and adding it again so it forgets it wants to delete it.
That's not an even it's trying to delete, but rather the calendar itself.
Interesting, I checked and the hash that it tries to delete does not exist in my calendars.
Any idea why the mac would try to do that?
Maybe I accidentally added a new calendar from the calendar.app and then removed it so now it tries to sync.
An easy way to get things to work again is to remove your calendar account from the mac and adding it again so it forgets it wants to delete it.
This might result in losing recently added events though.
This might result in losing recently added events though.
My bad, it looks like the events are synced properly, so it safe to do. That solved it for now, thanks.
Ah great. Please reopen if this happens again and wasn't just a one-time fluke. I think etesync-dav was behaving correctly here, though maybe it should be more aggressive in telling the mac that deletions are not allowed.
Thanks for all the info!
The last couple of days calendar is failing to sync with etesync. I have tried restarting both but it still doesn't work. It looks like calendar is trying to delete an event that does not exist, and then tries to access
/
which is forbidden.Any instructions on how to debug/fix this?