Repository navigation
Fix invalid UTF-8 when truncating long event fields - #368
Conversation
Signed-off-by: Adrian Groh <[email protected]>
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
lukasdotcom
left a comment
There was a problem hiding this comment.
Thanks @Gobidev for the pr.
summary/location/descriptionare truncated to 250 bytes withsubstr(), which can split a multibyte character and leave invalid UTF-8 in the generated event. The event then never imports: the insert intooc_calendarobjects_propsfails and it's retried on every sync (MariaDB showsIncorrect string value: '\xC3', PostgreSQLinvalid byte sequence). Switch those three fields tomb_strcut(), which keeps the 250-byte limit but cuts at character boundaries. Same fix as MarcelRobitaille#59. Already verified there on Nextcloud 35.0.1.