[Akonadi] [Bug 308122] After some weeks downtime, google calendar fetch fails. "The requested minimum modification time lies too far in the past"

[Dan Vrátil]

https://bugs.kde.org/show_bug.cgi?id=308122

Dan Vrátil <dvratil at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
   Version Fixed In|                            |4.10.4
         Resolution|---                         |FIXED
      Latest Commit|                            |http://commits.kde.org/kdep
                   |                            |im-runtime/d8a57f8a19f05a0f
                   |                            |84c8f7a9d48ea87775cfad45

--- Comment #5 from Dan Vrátil <dvratil at redhat.com> ---
Git commit d8a57f8a19f05a0f84c8f7a9d48ea87775cfad45 by Dan Vrátil.
Committed on 14/05/2013 at 15:35.
Pushed by dvratil into branch 'KDE/4.10'.

Force full-resync if last sync was more than 25 days ago

Fixes 'The requested minimum modification time lies too far in the past'
error from Google Calendar resource that users saw after they returned
from vacation :-)

Also simplifies the code and speeds up sync by not fetching all existing
items before fetching data from Google (I probably copy-pasted it from
somewhere in the early days without actually understanding what's going on)
FIXED-IN: 4.10.4

M  +38   -52   resources/google/calendar/calendarresource.cpp
M  +0    -1    resources/google/calendar/calendarresource.h
M  +8    -1    resources/google/calendar/resource_events.cpp
M  +7    -1    resources/google/calendar/resource_tasks.cpp

http://commits.kde.org/kdepim-runtime/d8a57f8a19f05a0f84c8f7a9d48ea87775cfad45

-- 
You are receiving this mail because:
You are on the CC list for the bug.