Use of uninitialized memory
I just noticed this in a valgrind log of the evolution-calendar-factory after starting Evolution:
==31736== Thread 46 pool-evolution-:
==31736== Conditional jump or move depends on uninitialised value(s)
==31736== at 0x11CED415E: e_etesync_connection_get_changes_sync (src/common/e-etesync-connection.c:760)
==31736== by 0x11722E004: ecb_etesync_get_changes_sync (src/calendar/e-cal-backend-etesync.c:193)
==31736== by 0x100888249: e_cal_meta_backend_get_changes_sync (e-cal-meta-backend.c:4886)
==31736== by 0x10087BCD3: ecmb_refresh_internal_sync (e-cal-meta-backend.c:743)
==31736== by 0x10087C07A: ecmb_refresh_thread_func (e-cal-meta-backend.c:808)
==31736== by 0x10085D70F: cal_backend_dispatch_thread (e-cal-backend.c:241)
==31736== by 0x10095ED94: g_thread_pool_thread_proxy (gthreadpool.c:354)
==31736== by 0x10095E667: g_thread_proxy (gthread.c:807)
==31736== by 0x10098AAF8: linux_pthread_proxy (gthread-posix.c:1254)
==31736== by 0x101CBF431: start_thread (in /usr/lib64/libpthread-2.31.so)
==31736== by 0x1016FF6D2: clone (in /usr/lib64/libc-2.31.so)