Clock and calendar tests fail with static void QOrganizerEDSEngine::itemsAsyncListed(ECalComponent*, time_t, time_t, FetchRequestData*)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Calendar App |
Fix Released
|
Undecided
|
Unassigned | ||
Ubuntu Clock App |
Fix Released
|
High
|
Unassigned | ||
Ubuntu UI Toolkit |
Fix Released
|
Undecided
|
Unassigned | ||
qtorganizer5-eds (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
ubuntu-ui-toolkit (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
It appears the bugfix for this bug; https:/
static void QOrganizerEDSEn
APPEND QOrganizerItemD
APPEND QOrganizerItemD
static void QOrganizerEDSEn
I'm not sure if calendar works after the fix as well, it seems like it too still suffers from the issue.
Some example runs;
http://
Related branches
- Nicholas Skaggs (community): Approve
- PS Jenkins bot: Approve (continuous-integration)
- Ubuntu Phablet Team: Pending requested
-
Diff: 151 lines (+35/-18)5 files modifiedqorganizer/qorganizer-eds-engine.cpp (+15/-0)
qorganizer/qorganizer-eds-fetchrequestdata.cpp (+12/-11)
tests/unittest/CMakeLists.txt (+2/-1)
tests/unittest/collections-test.cpp (+1/-1)
tests/unittest/event-test.cpp (+5/-5)
- Zsombor Egri: Approve
- PS Jenkins bot: Approve (continuous-integration)
- Nicholas Skaggs (community): Approve
-
Diff: 36 lines (+14/-1)2 files modifiedmodules/Ubuntu/Components/plugin/adapters/alarmsadapter_organizer.cpp (+13/-0)
tests/unit/tst_alarms/tst_alarms.cpp (+1/-1)
description: | updated |
Changed in qtorganizer5-eds (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in ubuntu-ui-toolkit: | |
milestone: | none → february-2014 |
status: | New → Fix Released |
Changed in ubuntu-calendar-app: | |
status: | New → Fix Released |
apparently this is caused because the app does not specify any date interval when querying for events. This can return a unlimited number of events. For example a event that has daily recurrence will appear several/unlimited times on the query. The proper fix for that is always use a date interval when querying for events.