lp:~zeitgeist/zeitgeist/sort-by-orig
- Get this branch:
- bzr branch lp:~zeitgeist/zeitgeist/sort-by-orig
Branch merges
- Markus Korn: Approve (code tests)
-
Diff: 191 lines (+81/-14)4 files modified_zeitgeist/engine/main.py (+10/-6)
test/data/twenty_events.js (+3/-3)
test/engine-test.py (+57/-0)
zeitgeist/datamodel.py (+11/-5)
Related bugs
Bug #487321: What value should subject.origin have? | High | Fix Released |
Related blueprints
Branch information
Recent revisions
- 1529. By Mikkel Kamstrup Erlandsen <kamstrup@delight>
-
Implement and unit test sorting and grouping by origin
Clean up some of the grouping logic. It was actually somehow working (we had passing test cases covering this) but the SQL looked high suspicious to me
- 1528. By Mikkel Kamstrup Erlandsen <kamstrup@delight>
-
Allow new origin-based ResultTypes in the core engine
- 1527. By Mikkel Kamstrup Erlandsen <kamstrup@delight>
-
Update description of subject.origin to reflect discussion from https:/
/bugs.launchpad .net/zeitgeist/ +bug/487321 Add new ResultTypes we need to sort by origin
- 1523. By Siegfried Gevatter
-
Remove return value from register_
data_source, it wasn't being send through D-Bus and is pointless anyway. Spotted by Michal Hruby (mhr3).
- 1522. By Markus Korn
-
- it always restores the values of os.environ if changed to zeitgeist
specific values
- make sure to call the test methods (self.assertEquals() etc.) in the main
process, and not in a callback, this exposes failures in the test report
- added RemoteTestCase.{deleteEventsAn dWait,findRelat edEventsAndWait } in
testutils.py
- small API CHANGE of the experimental DeleteEvents()-method: this method
now returns a time-tuple describing the intervall where events were
changed, otherwise there won't be any direct way to test this method
(without using a monitor)
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:zeitgeist/0.1