| Summary: | After some weeks downtime, google calendar fetch fails. "The requested minimum modification time lies too far in the past" | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] Akonadi | Reporter: | Andreas K. Huettel <dilfridge> |
| Component: | Google Resource | Assignee: | Daniel Vrátil <dvratil> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | GeoBaltz, kdepim-bugs, Mathias.Homann, mfraz74+kde |
| Priority: | NOR | ||
| Version: | 4.9 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/kdepim-runtime/d8a57f8a19f05a0f84c8f7a9d48ea87775cfad45 | Version Fixed In: | 4.10.4 |
| Sentry Crash Report: | |||
|
Description
Andreas K. Huettel
2012-10-09 12:46:46 UTC
I'm having the very same thing, whenever I use an account on my laptop that I only use once every few weeks. Confirmed, Calendar API allows to fetch only items changed within approximately last 25 days. When trying to request list of changes from deeper in the history, the API will return this error. Solution is probably to use timeMin argument when last update was more then 20 (?) days ago and fetch all events with dtStart>=timeMin. Using lastUpdated date, we can filter out events that were not changed between timeMin and now and use itemsRetrievedIncremental(). Having the same problem(KDE SC 4.10.2, openSUSE 12.3) - is there any workaround to get the calendar updated on this laptop, or do I have to delete the resource and start over? Sorry, not yet. You have to remove and add the resource again. 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 Is there any way of resetting the resource number back to zero? As in the akonadi_googlecalendar_X number? Yes, theoretically, by editing respective InstanceCounter in ~/.config/akonadi/agentsrc. There's not guarantee things won't go nuts however. Yes, that is the one I was on about. Just tried it and resetting the InstanceCounter doesn't work, it still increments to the next value. There's really no point in doing that. Just remove the resource and add it again. |