Activity log for bug #646124

Date Who What changed Old value New value Message
2010-09-23 16:17:06 Seif Lotfy bug added bug
2010-09-23 16:17:18 Seif Lotfy zeitgeist: assignee Seif Lotfy (seif)
2010-09-23 16:17:38 Seif Lotfy description In an attempt to work on bug #641968 I discovered that we some of us defer on the understanding of LeastRecentActor The documentation stated that LeastRecentActor = enum_factory(("The first event of each different actor")) Let's assume we have sequential events. (The actors are defined by numbers) 2, 1, 3, 2, 1, 4 So we have 4 different actors (1,2,3,4) and we want to sort them by least recent. the least recent is not 2 or 1 since they are used again at the end. the least recent is 3 This means LeastRecentActors should return the latest actors sorted ASC: 3, 2, 1, 4 and not 2, 1, 3, 4 When we look at LeastRecentSubjects = enum_factory(("One event for each subject only, " "ordered with oldest events first")) My understanding according to Siegfried is: <seif_> http://pastebin.com/zFWbMmEg <seif_> RainCT, <seif_> LeastRecentSubjects = enum_factory(("One event for each subject only, " <seif_> "ordered with oldest events first") <seif_> so i f i have <seif_> the subject <seif_> 1, 2, 1, 3, 4 <seif_> what do i get returned <seif_> 1, 2, 3, 4 <seif_> or <seif_> 2, 1, 3, 4 <seif_> ? <RainCT> seif_: the later <RainCT> for each subject you only look at the most recent one <seif_> ok then we should do the same for the actors :) <RainCT> Yes. Isn't it like this already? <seif_> no In that case if we follow this convention I can update the doc strings and already have the bug fix for both this bug and #641968 In an attempt to work on bug #641968 I discovered that we some of us defer on the understanding of LeastRecentActor The documentation stated that LeastRecentActor = enum_factory(("The first event of each different actor")) Let's assume we have sequential events. (The actors are defined by numbers) 2, 1, 3, 2, 1, 4 So we have 4 different actors (1,2,3,4) and we want to sort them by least recent. the least recent is not 2 or 1 since they are used again at the end. the least recent is 3 This means LeastRecentActors should return the latest actors sorted ASC: 3, 2, 1, 4 and not 2, 1, 3, 4 When we look at LeastRecentSubjects = enum_factory(("One event for each subject only, "   "ordered with oldest events first")) My understanding according to Siegfried is: <seif_> RainCT, <seif_> LeastRecentSubjects = enum_factory(("One event for each subject only, " <seif_> "ordered with oldest events first") <seif_> so i f i have <seif_> the subject <seif_> 1, 2, 1, 3, 4 <seif_> what do i get returned <seif_> 1, 2, 3, 4 <seif_> or <seif_> 2, 1, 3, 4 <seif_> ? <RainCT> seif_: the later <RainCT> for each subject you only look at the most recent one <seif_> ok then we should do the same for the actors :) <RainCT> Yes. Isn't it like this already? <seif_> no In that case if we follow this convention I can update the doc strings and already have the bug fix for both this bug and #641968
2010-09-23 16:18:47 Seif Lotfy branch linked lp:~seif/zeitgeist/fix-641968
2010-09-25 11:19:42 Seif Lotfy zeitgeist: importance Undecided Low
2010-09-25 11:19:48 Seif Lotfy zeitgeist: status New Triaged
2010-09-25 11:19:56 Seif Lotfy zeitgeist: milestone 0.6
2010-09-25 11:43:05 Seif Lotfy branch linked lp:~zeitgeist/zeitgeist/fix-646124
2010-09-25 11:47:40 Seif Lotfy zeitgeist: status Triaged In Progress
2010-09-25 12:32:05 Seif Lotfy zeitgeist: status In Progress Fix Committed
2010-09-25 12:32:08 Seif Lotfy zeitgeist: milestone 0.6 0.5.2
2010-09-25 13:14:27 Launchpad Janitor branch linked lp:zeitgeist
2010-09-25 16:10:11 Siegfried Gevatter zeitgeist: milestone 0.5.2 0.6
2010-09-25 16:10:27 Siegfried Gevatter zeitgeist: milestone 0.6 0.5.2
2010-09-26 18:22:57 Siegfried Gevatter zeitgeist: status Fix Committed Fix Released
2010-09-26 20:27:28 Launchpad Janitor branch linked lp:~zeitgeist-packagers/zeitgeist/debian