https://bugs.freedesktop.org/show_bug.cgi?id=86463 --- Comment #2 from renato filho <renatox(a)gmail.com&gt; --- I have implemented a very simple way to configure the start date, that can be configure on the calendar source and is used by caldav source implementation. Some points that still improvements: 1- Find a better name for the property name "startDate" is too generic; 2- The current configuration key "stateDate" appears for all kind of sources would be nice to make it available only for calendar sources (is that possible). Check attachments with my patch. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=86463 --- Comment #4 from Patrick Ohly <patrick.ohly(a)gmx.de&gt; --- Comment on attachment 109732 --> https://bugs.freedesktop.org/attachment.cgi?id=109732 remove unrelated changes Is the expectation that StartDate gets updated regularly by the user? When set only once, the calendar will start to grow over time again, it will just start smaller. I'm not sure how significant that will be and in which cases - a slow sync perhaps. The alternative would be to have a relative time and sync events falling into the last n days, for example. When a synchronized event falls out of that time range, it should (?) be removed locally. Not sure whether additional code is needed to achieve that. The same situation occurs when the user moves the startDate forward after having synchronized. Another corner case is events created locally outside of the time range. I suppose they shall and will be synchronized to the server. When they then get edited on the server, is the change synced back? The patch itself looks okay at first glance. "Leve it empty" is a type (should be "Leave"). A comment that this is only implement for CalDAV would be useful. registry.push_back() and sourcePropCalendarStartDate don't line up with the rest of the surrounding code - were tabs used for formatting? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=86463 --- Comment #6 from Patrick Ohly <patrick.ohly(a)gmx.de&gt; --- Renato, can you investigate what happens in the corner cases that I mentioned? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=86463 --- Comment #7 from Patrick Ohly <patrick.ohly(a)gmx.de&gt; --- Beware that the patches as they were proposed caused bug #89853. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=86463 --- Comment #9 from renato filho <renatox(a)gmail.com&gt; --- Created attachment 114893 --> https://bugs.freedesktop.org/attachment.cgi?id=114893&action=edit full log of invalid sync -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=86463 --- Comment #11 from renato filho <renatox(a)gmail.com&gt; --- After this patch changing the syncInterval causes sync to update events that does not changed. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=86463 renato filho <renatox(a)gmail.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #114894|text/plain |application/x-bzip2 mime type| | -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=86463 --- Comment #13 from renato filho <renatox(a)gmail.com&gt; --- As you can see on target log: on Client on Server Added: 0 2 Deleted: 0 0 Updated: 0 0 Rejected with error: 0 0 Content Data Bytes sent: 1663 Content Data Bytes received: 0 Duration of sync [seconds]: 1 It says that 2 events was added on the server. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=86463 Patrick Ohly <patrick.ohly(a)gmx.de&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Assignee|syncevolution-issues@syncev |renatox(a)gmail.com |olution.org | --- Comment #15 from Patrick Ohly <patrick.ohly(a)gmx.de&gt; --- Patch needs further work, see comment #14. The investigation and/or documentation of corner case handling (= events falling out of the time range) is also still missing. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=86463 Patrick Ohly <patrick.ohly(a)gmx.de&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #114894|0 |1 is obsolete| | --- Comment #17 from Patrick Ohly <patrick.ohly(a)gmx.de&gt; --- Comment on attachment 114894 --> https://bugs.freedesktop.org/attachment.cgi?id=114894 target full log See comment #14. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=86463 GitLab Migration User <gitlab-migration(a)fdo.invalid&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|ASSIGNED |RESOLVED --- Comment #19 from GitLab Migration User <gitlab-migration(a)fdo.invalid&gt; --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/41. -- You are receiving this mail because: You are on the CC list for the bug.