[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors
** Changed in: zeitgeist
Status: Fix Committed => Fix Released
--
Wrong understanding of the LeastRecentActors
https://bugs.launchpad.net/bugs/646124
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: Fix Released
Bug 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:
RainCT,
LeastRecentSubjects = enum_factory(("One event for each subject only, "
"ordered with oldest events first")
so i f i have
the subject
1, 2, 1, 3, 4
what do i get returned
1, 2, 3, 4
or
2, 1, 3, 4
?
seif_: the later
for each subject you only look at the most recent one
ok then we should do the same for the actors :)
Yes. Isn't it like this already?
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
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors
** Changed in: zeitgeist
Milestone: 0.5.2 => 0.6
** Changed in: zeitgeist
Milestone: 0.6 => 0.5.2
--
Wrong understanding of the LeastRecentActors
https://bugs.launchpad.net/bugs/646124
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: Fix Committed
Bug 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:
RainCT,
LeastRecentSubjects = enum_factory(("One event for each subject only, "
"ordered with oldest events first")
so i f i have
the subject
1, 2, 1, 3, 4
what do i get returned
1, 2, 3, 4
or
2, 1, 3, 4
?
seif_: the later
for each subject you only look at the most recent one
ok then we should do the same for the actors :)
Yes. Isn't it like this already?
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
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors
** Branch linked: lp:zeitgeist
--
Wrong understanding of the LeastRecentActors
https://bugs.launchpad.net/bugs/646124
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: Fix Committed
Bug 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:
RainCT,
LeastRecentSubjects = enum_factory(("One event for each subject only, "
"ordered with oldest events first")
so i f i have
the subject
1, 2, 1, 3, 4
what do i get returned
1, 2, 3, 4
or
2, 1, 3, 4
?
seif_: the later
for each subject you only look at the most recent one
ok then we should do the same for the actors :)
Yes. Isn't it like this already?
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
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors
** Changed in: zeitgeist
Status: In Progress => Fix Committed
** Changed in: zeitgeist
Milestone: 0.6 => 0.5.2
--
Wrong understanding of the LeastRecentActors
https://bugs.launchpad.net/bugs/646124
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: Fix Committed
Bug 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:
RainCT,
LeastRecentSubjects = enum_factory(("One event for each subject only, "
"ordered with oldest events first")
so i f i have
the subject
1, 2, 1, 3, 4
what do i get returned
1, 2, 3, 4
or
2, 1, 3, 4
?
seif_: the later
for each subject you only look at the most recent one
ok then we should do the same for the actors :)
Yes. Isn't it like this already?
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
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors
** Branch linked: lp:~zeitgeist/zeitgeist/fix-646124
** Changed in: zeitgeist
Status: Triaged => In Progress
--
Wrong understanding of the LeastRecentActors
https://bugs.launchpad.net/bugs/646124
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: In Progress
Bug 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:
RainCT,
LeastRecentSubjects = enum_factory(("One event for each subject only, "
"ordered with oldest events first")
so i f i have
the subject
1, 2, 1, 3, 4
what do i get returned
1, 2, 3, 4
or
2, 1, 3, 4
?
seif_: the later
for each subject you only look at the most recent one
ok then we should do the same for the actors :)
Yes. Isn't it like this already?
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
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors
** Changed in: zeitgeist
Importance: Undecided => Low
** Changed in: zeitgeist
Status: New => Triaged
** Changed in: zeitgeist
Milestone: None => 0.6
--
Wrong understanding of the LeastRecentActors
https://bugs.launchpad.net/bugs/646124
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: Triaged
Bug 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:
RainCT,
LeastRecentSubjects = enum_factory(("One event for each subject only, "
"ordered with oldest events first")
so i f i have
the subject
1, 2, 1, 3, 4
what do i get returned
1, 2, 3, 4
or
2, 1, 3, 4
?
seif_: the later
for each subject you only look at the most recent one
ok then we should do the same for the actors :)
Yes. Isn't it like this already?
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
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors
We discussed this issue on IRC, a summary:
* the current definition of LeastRecentActors is wrong, it should be
"application I have not used for the longest time"
* we need a new ResultType for the old definition ("The first event of each
different actor"), something like OldestActor
The plan to fix this bug is:
1.) Fix the initial issue described in bug 641968 (LeastRecentActors is not
working together with templates)
2.) land the fix for 1.) in lp:zeitgeist
3.) rename LeastRecentActor into something like OldestActor (we still need a
smart name for this)
4.) reimplement LeastRecentActor to return the result as descibed in the
various examples here
5.) land 3.) and 4.) to lp:zeitgeist at the same time
--
Wrong understanding of the LeastRecentActors
https://bugs.launchpad.net/bugs/646124
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: New
Bug 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:
RainCT,
LeastRecentSubjects = enum_factory(("One event for each subject only, "
"ordered with oldest events first")
so i f i have
the subject
1, 2, 1, 3, 4
what do i get returned
1, 2, 3, 4
or
2, 1, 3, 4
?
seif_: the later
for each subject you only look at the most recent one
ok then we should do the same for the actors :)
Yes. Isn't it like this already?
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
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors
On Fri, Sep 24, 2010 at 2:59 PM, Markus Korn wrote:
> Ok, maybe there were some misunderstandings, I was looking for some real
> life questions...
> Let's assume this one:
> "What were the first three actors accessing '/home/markus/seif.txt'"
>
This is not the same as "What were the lease recent actors accessing
'/home/markus/seif.txt'
One will give u the oldest events and the other will give u the latest
events sorted ASC.
> With the current definition of LeastRecentActors the query would look like
> >>> template = Event.new_for_values(subject_uri="/home/markus/seif.txt")
> >>> events = FindEvents(TimeRange.Always(), [template,], Any, 3,
> LeastRecentActor)
> >>> actors = [e.actor for e in events]
>
> This would not work anymore if we do the change you propose. So what I want
> you to tell me is:
> * How will the query look like in your definition?
>
The query will be the same the return however won't
> * Can you give me a similar question which gives a usecase for your
> definition?
>
I just did :)
>
> --
> Wrong understanding of the LeastRecentActors
> https://bugs.launchpad.net/bugs/646124
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Zeitgeist Framework: New
>
> Bug 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:
>
> RainCT,
> LeastRecentSubjects = enum_factory(("One event for each subject
> only, "
>"ordered with oldest events first")
> so i f i have
> the subject
> 1, 2, 1, 3, 4
> what do i get returned
> 1, 2, 3, 4
> or
> 2, 1, 3, 4
> ?
> seif_: the later
> for each subject you only look at the most recent one
> ok then we should do the same for the actors :)
> Yes. Isn't it like this already?
> 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
>
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/zeitgeist/+bug/646124/+subscribe
>
--
This is me doing some advertisement for my blog http://seilo.geekyogre.com
--
Wrong understanding of the LeastRecentActors
https://bugs.launchpad.net/bugs/646124
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: New
Bug 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:
RainCT,
LeastRecentSubjects = enum_factory(("One event for each subject only, "
"ordered with oldest events first")
so i f i have
the subject
1, 2, 1, 3, 4
what do i get returned
1, 2, 3, 4
or
2, 1, 3, 4
?
seif_: the later
for each subject you only look at the most recent one
ok then we should do the same for the actors :)
Yes. Isn't it like this already?
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
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors
2010/9/24 Markus Korn :
> * Can you give me a similar question which gives a usecase for your
> definition?
"Which were the applications I haven't used for the most time?"
--
Siegfried-Angel Gevatter Pujals (RainCT)
Free Software Developer 363DEAE3
--
Wrong understanding of the LeastRecentActors
https://bugs.launchpad.net/bugs/646124
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: New
Bug 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:
RainCT,
LeastRecentSubjects = enum_factory(("One event for each subject only, "
"ordered with oldest events first")
so i f i have
the subject
1, 2, 1, 3, 4
what do i get returned
1, 2, 3, 4
or
2, 1, 3, 4
?
seif_: the later
for each subject you only look at the most recent one
ok then we should do the same for the actors :)
Yes. Isn't it like this already?
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
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors
Ok, maybe there were some misunderstandings, I was looking for some real life
questions...
Let's assume this one:
"What were the first three actors accessing '/home/markus/seif.txt'"
With the current definition of LeastRecentActors the query would look like
>>> template = Event.new_for_values(subject_uri="/home/markus/seif.txt")
>>> events = FindEvents(TimeRange.Always(), [template,], Any, 3,
LeastRecentActor)
>>> actors = [e.actor for e in events]
This would not work anymore if we do the change you propose. So what I want you
to tell me is:
* How will the query look like in your definition?
* Can you give me a similar question which gives a usecase for your
definition?
--
Wrong understanding of the LeastRecentActors
https://bugs.launchpad.net/bugs/646124
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: New
Bug 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:
RainCT,
LeastRecentSubjects = enum_factory(("One event for each subject only, "
"ordered with oldest events first")
so i f i have
the subject
1, 2, 1, 3, 4
what do i get returned
1, 2, 3, 4
or
2, 1, 3, 4
?
seif_: the later
for each subject you only look at the most recent one
ok then we should do the same for the actors :)
Yes. Isn't it like this already?
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
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors
On Fri, Sep 24, 2010 at 12:37 PM, Markus Korn wrote:
> Seif, can you please give tow different usecases, one for the old
> definition of LeastRecentActors and one for your new one. Please also
> try to explain how changing the definition will influence real world
> usecases.
>
> --
> Wrong understanding of the LeastRecentActors
> https://bugs.launchpad.net/bugs/646124
> You received this bug notification because you are a member of Zeitgeist
> Framework Team, which is subscribed to Zeitgeist Framework.
>
> Status in Zeitgeist Framework: New
>
> Bug 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:
>
> RainCT,
> LeastRecentSubjects = enum_factory(("One event for each subject
> only, "
>"ordered with oldest events first")
> so i f i have
> the subject
> 1, 2, 1, 3, 4
> what do i get returned
> 1, 2, 3, 4
> or
> 2, 1, 3, 4
> ?
> seif_: the later
> for each subject you only look at the most recent one
> ok then we should do the same for the actors :)
> Yes. Isn't it like this already?
> 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
>
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~zeitgeist
> Post to : zeitgeist@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zeitgeist
> More help : https://help.launchpad.net/ListHelp
>
Ok let me try to explain it in terms of real applications:
10:00 Firefox access youtube.com
10:01 Opera access google.com
10:02 Chrome access youtube.com
10:03 Firefox access facebook.com
10:04 Opera access twitter.com
10:05 Firefox access google.com
Currently LeastRecentActor would give us:
10:00 Firefox access youtube.com
10:01 Opera access google.com
10:02 Chrome access youtube.com
Where it should give us:
10:02 Chrome access youtube.com
10:04 Opera access twitter.com
10:05 Firefox access google.com
because with the same criteria LeastRecentSubject gives us:
10:02 Chrome access youtube.com
10:03 Firefox access facebook.com
10:04 Opera access twitter.com
10:05 Firefox access google.com
and not:
10:00 Firefox access youtube.com
10:01 Opera access google.com
10:03 Firefox access facebook.com
10:04 Opera access twitter.com
Real World use cases would be changed in terms of awaited results. I dont
know how to explain it.
--
Wrong understanding of the LeastRecentActors
https://bugs.launchpad.net/bugs/646124
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: New
Bug 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:
RainCT,
LeastRecentSubjects = enum_factory(("One event for each subject only, "
"ordered with oldest events first")
so i f i have
the subject
1, 2, 1, 3, 4
what do i get returned
1, 2, 3, 4
or
2, 1, 3, 4
?
seif_: the later
for each subject you only look at the most recent one
ok then we should do the same for the actors :)
Yes. Isn't it like this already?
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
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors
Seif, can you please give tow different usecases, one for the old
definition of LeastRecentActors and one for your new one. Please also
try to explain how changing the definition will influence real world
usecases.
--
Wrong understanding of the LeastRecentActors
https://bugs.launchpad.net/bugs/646124
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: New
Bug 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:
RainCT,
LeastRecentSubjects = enum_factory(("One event for each subject only, "
"ordered with oldest events first")
so i f i have
the subject
1, 2, 1, 3, 4
what do i get returned
1, 2, 3, 4
or
2, 1, 3, 4
?
seif_: the later
for each subject you only look at the most recent one
ok then we should do the same for the actors :)
Yes. Isn't it like this already?
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
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors
Exactly.
The current docstring matches the current returns. IMHO both are wrong
according to my and Siegfried's definition of LeastRecentActor. I do agree with
your proposal of changing the docstring to "The most recent event for each
subject, ordered with the oldest events first". Because it will match our
definition of LeastRecentSubject. My concern is if its a API break?
--
Wrong understanding of the LeastRecentActors
https://bugs.launchpad.net/bugs/646124
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: New
Bug 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:
RainCT,
LeastRecentSubjects = enum_factory(("One event for each subject only, "
"ordered with oldest events first")
so i f i have
the subject
1, 2, 1, 3, 4
what do i get returned
1, 2, 3, 4
or
2, 1, 3, 4
?
seif_: the later
for each subject you only look at the most recent one
ok then we should do the same for the actors :)
Yes. Isn't it like this already?
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
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 646124] Re: Wrong understanding of the LeastRecentActors
Taking the LeastRecentSubjects example. I'm going to assume you have
time=0 on the left and time>0 on the right: 1, 2, 1, 3, 4.
Then "One event for each subject only, ordered with oldest events first"
would definitely mean: 1, 2, 3, 4. If we are sorting like RainCT is
proposing then the docstring should probably be "The most recent event
for each subject, ordered with the oldest events first" or something
like that.
That said I am actually not sure at all what the right API is. WHich use
cases do we have?
--
Wrong understanding of the LeastRecentActors
https://bugs.launchpad.net/bugs/646124
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: New
Bug 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:
RainCT,
LeastRecentSubjects = enum_factory(("One event for each subject only, "
"ordered with oldest events first")
so i f i have
the subject
1, 2, 1, 3, 4
what do i get returned
1, 2, 3, 4
or
2, 1, 3, 4
?
seif_: the later
for each subject you only look at the most recent one
ok then we should do the same for the actors :)
Yes. Isn't it like this already?
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
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
