[CalendarServer-users] Connection aborted - took too long to close

[Jacques Distler]

> There is one known issue in 5.3 regarding how we handle updating calendar event data when the format changes (as it has recently). In 5.3, the approach is to leave the data in the old format until it is requested, and then update it on the fly as it is vended to the client. This fails when there are enough events being 'touched' by the request that the processing time for doing the format upgrades exceeds the client's request timeout threshold. This is fixed in 5.4-dev.

Is there (say) a commandline utility to upgrade the data to the new format?

Or some other way to address these (rather persistent) timeouts?

FWIW, I ran calendarserver_verify_data and everything checked out OK.

JD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 235 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.macosforge.org/pipermail/calendarserver-users/attachments/20150205/4393f654/attachment.sig>