CalendarSync icon indicating copy to clipboard operation
CalendarSync copied to clipboard

Stateless CLI tool to sync calendars across different calendaring systems.

Results 26 CalendarSync issues
Sort by recently updated
recently updated
newest added

Making sure we're retrieving events in UTC and write them in the local timezone of the user.

Decrypting the credentials requires a lot of memory, such that later garbage collections only happen after doubling that memory usage again. Explicitly run a GC to reset the memory usage...

The policy can be reused, thus there's no need to recreate it for every processed calendar event. Inspired by https://github.com/inovex/CalendarSync/issues/180 . But this barely changes the memory usage.

Enabling data race detection should be sufficient for release builds. Helps with https://github.com/inovex/CalendarSync/issues/180 when building from source. Release builds never used that flag.

As the whole request body is read using io.ReadAll, thus the request can be freed immediately afterwards. Might help with https://github.com/inovex/CalendarSync/issues/180 .

When using KeepAttendees (https://github.com/inovex/CalendarSync/blob/e449ad66e123d26ea2b590b9fcd0cebc3afe23b6/internal/transformation/keepAttendees.go#L22-L44) the email address is converted into some hash@localhost, but the displayname should then contain either the name or (email)address of the attendee. Unfortunately for my setup...