What to do if an event is not found or blocked when calling GetEvents (or its engine equivalent)
Bug #495392 reported by
Markus Korn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zeitgeist Framework |
Fix Released
|
Critical
|
Markus Korn |
Bug Description
Right now GetEvents raises a KeyError whenever any event is either not found or blocked by an extension. As good as this solution was in case of not found events it turns out to be bad for blocked events.
I think there are two possible solutions:
* adding a NULLEvent, a somehow designed event datastructure which indicates "cannot find an event (with this id)"
* raising a KeyError which somehow contains all failing/blocked event-ids. The client can now make another GetEvents call but remove all failing ids from the arguments
If we manage to find a good NULLEvent I think this solution makes the most sense.
Related branches
lp:~thekorn/zeitgeist/null_event
(Merged)
Changed in zeitgeist: | |
milestone: | none → 0.3.1 |
importance: | Undecided → Critical |
Changed in zeitgeist: | |
status: | In Progress → Fix Committed |
Changed in zeitgeist: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The attached branch adds a NULL_EVENT to the datamodel.
I think the branch is not ready to be merged yet, still needs some tweaks.
But it should give the general idea of how this could work.
The ZeitgeistClient automatically translates a received NULL_EVENT to None.