I don't know a lot about nose, but can't you use nose to run the tests
we already have and then accomplish what you want?
My primary concern here is probably keeping the third party deps to a
minimum - also for developers.
Also I don't quite agree that it is so hard to run individual tests...
jus
This is a standardized DBus Properties interface we can use for this...
We might also want to version our DBus interfaces (like fx. Tracker does
since 0.7), but that is not exactly what this bug is about...
--
Add engine version identifier and expose this ID over the DBus API
https://bugs.launch
I think it looks really good. Easy to extend with new properties,
readable, as well as writable. You should propose the branch for a
merge.
--
Add engine version identifier and expose this ID over the DBus API
https://bugs.launchpad.net/bugs/462890
You received this bug notification because you a
If you can convert test/remote-test.py to use the unittest module that
is fine with me. I can not see any code in your linked branch though..?
--
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make test/remote-test.py proper
unittests
https://bugs.launchpad.net/bugs/483550
You received this bug n
Public bug reported:
During the hackfest we decided on a new logo (small blue ghost). We
should update our presence on the web with this logo (ie. launchpad and
elsewhere).
I believe that Seif has the logo somewhere...
** Affects: zeitgeist
Importance: Medium
Assignee: Seif Lotfy (seif
+1
--
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to
the engine configurable
https://bugs.launchpad.net/bugs/483556
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
Status in Zeitgeist
There is quite a lot of whitespace twiddling in your branch, making it
hard to review...
I can not see exactly how you plan to load the extensions and how you
plan to use the __public_methods__ of the extensions..?
--
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions t
Ok. Looks sane to me, but I haven't tested it. If the three(?) tests
still run and pass fine its fine to merge I think
--
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make test/remote-test.py proper
unittests
https://bugs.launchpad.net/bugs/483550
You received this bug notification because you
We don't use seconds. We use milliseconds since the Unix epoch.
I dislike floating point timestamps because of two things:
* Python is the only language I have ever heard of that use floats for
timestamps
* Float-comparisons (and thus db-indexes) are less effective than integer
comparisons
-
I think that extensions should expose their own DBus APIs. The engine
could expose its server-object to allow extensions to do this cleanly...
Regarding the two underscores; the gobject bindings use such constructs
as well (for __properties__ and __signals__). So if we have a *really*
good reason
>> We don't use seconds. We use milliseconds since the Unix epoch.
>Do we?
I believe you meant to say "o rly?!" :-) Anyway, in the places where I've coded
I've used int(time.time()*1000) and time() returns seconds since the Epoch...
While walking the dog I had some further thoughts on why reals/
Siegfried stated on IRC yesterday that he was in favor of the
milliesecond resolution using an INTEGER column (ie. what we have now).
I think this means that we have rough consensus..?
As for use cases with sub-second resolution think of messaging (IRC,
IM). If I continuously say "spam" on IRC I c
I think I like the engine.extensions.some_extension_method() approach
the best.
This way alternate extensions can provide the same method and the caller
does not need to know who implements it.
--
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to
the engine configu
For duplicate events this I think that Markus' proposal is OK. But do
we have any other error scenarios when inserting events? What is the
solution in this case then?
--
Dont' raise an exception when a duplicate event is detected
https://bugs.launchpad.net/bugs/485433
You received this bug notif
2009/11/19 Jason Smith :
> Zeitgeist Developers,
>
> There is an amazing amount of activity surrounding the happenings of
> Zeitgeist. Lots of excitement going on and obviously Zeitgeist will
> continue to be an important part of the linux experience in the coming
> years. Zeitgeist has not been wi
Is there a related branch?
I am also wondering if we can in some way hook us into the Tracker
eplugin?
--
create an external dataprovider for evolution
https://bugs.launchpad.net/bugs/485698
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant
Sorry; in the second paragraph above I meant "... events CAN'T have
a..."
--
Using filters (text match / exclusion / etc)
https://bugs.launchpad.net/bugs/485966
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
Status i
For this question to make sense you have to give a use case and explain
why it is not good enough to filter out events manually in the Firefox
example.
For nitpicking: events can have a "title that contains zeitgeist". They
can have a subject with text field containing 'zeitgeist'. If we want to
m
I think a nice default is to use the timestamp of object creation time.
That was the idea behind the test at least, and indeed it also worked
like that at some point (where the test worked). Otoh - the engine will
use the current time as timestamp if the incoming event doesn't have
one, so it might
@Seif: I think we can allow empty timestamps for convenience. And as I
said in comment 1 paragraph 3; we meassure time in milliseconds, hence
timestamps are genrated with int(time.time()*1000).
--
testInsertGetWithoutTimestamp testcase fails
https://bugs.launchpad.net/bugs/486996
You received thi
@Seif: I wouldn't have to care about the timestamp format when sending
events if my app doesn't need high precision timing. Just create the
Event instance and send it along. Recall that not all apps will be
written in Python and using our client libs...
--
testInsertGetWithoutTimestamp testcase f
WHY NOT?
--
Origin
https://bugs.launchpad.net/bugs/487321
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
Status in Zeitgeist Engine: New
Bug description:
>> + origin =
>> info.
I'll do this tonight, and update the unit tests accordingly
** Changed in: zeitgeist
Assignee: Seif Lotfy (seif) => Mikkel Kamstrup Erlandsen (kamstrup)
--
Dont' raise an exception when a duplicate event is detected
https://bugs.launchpad.net/bugs/485433
You received this bug
Yes. Plugins *must* send the timestamps in millis since the Epoch. If
apps only use second granularity then we will have three zeroes in the
end of the timestamps.
--
Use timestamps with milliseconds granularity (was: use REAL)
https://bugs.launchpad.net/bugs/483603
You received this bug notifica
Yeah. We had a discussion about this at the hackfest and everyone agreed
that origin must be a property of the subject(s). So the meaning og
origin is "where does the subject come from?". For files it is the
parent folder. For websites it is the root URL (eg. http://youtube.com).
We do need to fig
Fixed in revision #1157
** Changed in: zeitgeist
Status: Triaged => Fix Released
--
Dont' raise an exception when a duplicate event is detected
https://bugs.launchpad.net/bugs/485433
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant f
Fixed in r1158
** Changed in: zeitgeist
Status: Triaged => Fix Released
--
testInsertGetWithoutTimestamp testcase fails
https://bugs.launchpad.net/bugs/486996
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
St
Siegfried, I think you make a good case. However I don't see it
conflicting with what we have now though. Whether origin is something on
the event or the subject(s) is purely a matter of how one looks at it
now that we have a 1 to 1 mapping between events and subjects in the db.
The tricky part is
Markus - we already have a DeleteEvents() method taking an array of ids.
Just do FindEventIds(templates) and pass them to DeleteEvents. This
makes it easy to do highly advanced event deletion schemes.
As for blacklisting this is really an issue in apps pushing events to
Zeitgeist I think.
--
Zei
I think that Siegfried has an important point. Since we like to relay
events around the system the Zeitgeist core will need a blacklisting
mechanism. There are several steps in such a solution as I see it...
We need a matches_template(event_templ) method on the Event class. This
will be mighty han
Yeah, we've got the json importer now. That helps a lot at least.
--
zeitgeist needs a more powerful testing framework
https://bugs.launchpad.net/bugs/435099
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Status i
I am pretty sure that the reason for this bug is that we would at times
try to decode an already decoded unicode string within our magical
UnicodeCursor class. I fixed this in lp:zeitgeist r1164.
--
Problems with unicode
https://bugs.launchpad.net/bugs/488327
You received this bug notification be
I am wondering how I can link to a particular revision inside a branch in
launchpad bugs? Testing:
lp:zeitgeist:1164
1164:lp:zeitgeist
--
Problems with unicode
https://bugs.launchpad.net/bugs/488327
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the reg
Fixed in r1166. We had another double decode of a unicode string in
querymancer.
** Changed in: zeitgeist
Status: Confirmed => Fix Released
--
Problems with unicode
https://bugs.launchpad.net/bugs/488327
You received this bug notification because you are a member of
Zeitgeist-Engine, whic
>> templates they want to listen for. And then we only notify apps that
>> have registered matching templates.
>
>Is this even possible at all with D-Bus?
Yes. The direct solution is to have clients register some callback
interface. The more elegant approach would be to send directed signals.
Then
This is a coindidental match. The event.id column is not a primary key
(as rowid is). We can have multiple subjects/event which will give more
than one row with the same event id.
** Changed in: zeitgeist
Status: New => Invalid
--
DB BUG: event id column is redundant
https://bugs.launchpa
How can you talk to Zeitgeist over XPCOM? Is there some bridging
mechanism? Otherwise it might be useful to use a real DBus impl. for
Xulrunner http://wiki.github.com/FireRabbit/mozjs-dbus
--
firefox extension: use XPCOM instead of communicating via files
https://bugs.launchpad.net/bugs/488656
Yo
Ah, now I get it. You want to load a Zeitgeist XPCOM component, written
in Python, into Firefox, and then from that component import DBus (or
simply zeitgeist.client.ZeitgeistClient). This component is then used to
implement the extension in Javscript, or am I out on a limb?
--
firefox extension:
I am unsure what to do. I, for one, have several versions of Firefox
installed. To identify which one sending the event we'd need the whole
path to the .desktop file. OTOH getting the correct path to the .desktop
file might not always be easy.
In the .recently-used.xbel apps are identified simply
We now have debug statements with timing and count for insert, find, and
get.
** Changed in: zeitgeist
Status: New => Fix Released
--
add more logging statements to the engine
https://bugs.launchpad.net/bugs/488067
You received this bug notification because you are a member of
Zeitgeist-E
this please ping me...
** Affects: zeitgeist
Importance: High
Assignee: Mikkel Kamstrup Erlandsen (kamstrup)
Status: Confirmed
** Changed in: zeitgeist
Status: New => Confirmed
** Changed in: zeitgeist
Importance: Undecided => High
** Changed in: zeitgeist
Assign
Public bug reported:
We should cache the full Event objects in an LRUCache (of size something
like 500 or less). We can update the cache in InsertEvents() and
GetEvents(). The primary idea behind it is to massively speed up
GetEvents().
Anyway not hugely important, just an optimization.
** Affec
This bug is mostly about eactly what we want to store in origin, and how
to interpret origin exactly. I am deferring it to 0.3.1 because it's
unrealistic that we get full clarity on this before the weekend.
** Changed in: zeitgeist
Milestone: 0.3.0 => 0.3.1
--
Origin
https://bugs.launchpad.n
Do we really want to block 0.3.0 because of this bug? I would say no,
otherwise we will ship some very untested code if we want to ship 0.3.0
this weekend. I say defer to 0.3.1, it's only a micro API break.
--
Using filters (text match / exclusion / etc)
https://bugs.launchpad.net/bugs/485966
You
I believe Markus' branch was merged and the focus stuff removed for now?
So we can close this bug?
--
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make the loading of extensions to
the engine configurable
https://bugs.launchpad.net/bugs/483556
You received this bug notification because you are
Hi there,
We a prepping up for rolling our first development release in the
Zeitgeist 0.3 series (which will lead up to a stable 0.4 eventually).
Our plan is to roll the release this weekend.
So developers, please have a look over launchpad (fx. starting at
https://launchpad.net/zeitgeist/+milest
If we want to re-instate the old system it is a matter of a few lines.
But that would be a step back IMHO. And writing a full template based
notification system could not be done in two hours by one. It's not a
huge task, but definitely more than two hours :-)
Besides, I really think we should sto
Let me add a comment here on why we can't just emit a signal to
everyone...
In the future it is not impossible that many apps are connected to
Zeitgeist. Indeed if we have a hook in Gtk+ or Glib then *all* apps are
connected to us. Thus we'd send a signal to all desktop processes -
waking them up
I think I read somewhere in the Tracker changelogs that they committed a
fix for this, but maybe I mistook a normal comment on the matter as a
real committed fix...
Regarding 0.3 status I think we should ship 0.3.0 without it. There's
nothing stopping us having 0.3.1 next week already of we have g
I am looking into the directed signals approach, and from a look at the
DBus spec this should be possible. If we can somehow create our own
dbus.lowlevel.SignalMessage then we can call
set_destination(unique_name) on that. See
http://dbus.freedesktop.org/doc/dbus-python/api/. Alse see
http://dbus.f
Ok. I think I know how to do this now. I just need to find the time to
actually write the code :-)
Look at the nested emit_signal() method here:
http://dbus.freedesktop.org/doc/dbus-python/api/dbus.decorators-
pysrc.html#signal
--
Add event notification and subscription system
https://bugs.launc
Public bug reported:
The method GetHighestTimestampForActor is superfluous as far as I can
tell. It can be simply done fully client side by using FindEventIds like
so:
template = Event.new_for_values(actor="gedit")
ids = FindEventIds(TimeRange.until_now(), [template], StorageState.Any, 1,
Result
Public bug reported:
This is a reminder bug.
We need to write a "storage monitor" that manage the various storage
mediums we can have event subjects stored on. The storage monitor should
write any changes back to the 'storage' table in the DB.
What we need to track is connection and disconnectio
** Changed in: zeitgeist
Status: New => Triaged
** Changed in: zeitgeist
Assignee: (unassigned) => Mikkel Kamstrup Erlandsen (kamstrup)
** Changed in: zeitgeist
Importance: Undecided => Medium
** Changed in: zeitgeist
Milestone: None => 0.3.0
--
GetHighestTimes
I added code to check if a given Event matches some tempalte event.
We'll need that for notifications and bklacklisting. We don't have a
method to check for strict equality though afaik...
--
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] move code to compare two
event/subject objects to the actu
Cool that you did this test Markus! I am a bit troubled by the results
though...
I fear that signals are by definition always broadcasted. We may be able
to work around this by setting a match rule on each signal connection on
the client side, but I am not sure... Something like adding a named
par
I think open/close/modify makes the most sense. I prefer 'modify' over
'save' since fx. editing a contact or something like that is done in an
instant-apply dialog, without any notion of "saving".
Of course this whole deal is just a corner of our bigger problem - that
we need an event ontology. I'
This bug is probably not in client.py, but rather inside
resonance_engine.py, where we generate the SQL in find_eventids(). If
you can write a test case that triggers this, then that would be great.
I don't know what Siegfrieds state of the no-more-querymancer branch is
- the SQL generation code i
Hi,
On behalf of the Zeitgeist team I am proud to announce our first
development release, Zeitgeist 0.3.0, leading up to what will be our
stable series which will be 0.4. It is our intent to aim for a 1.0
release as soon as we feel good about the stable series, but that is
still a bit in the futur
2009/12/1 Neil Jagdish Patel :
> Hey,
>
> Congratulations :)
>
> I've got it built and running, however have nothing to test it with --
> have the tests been ported over to the new API? They seem to fail with
> broken D-Bus signatures. Also, are there any front-ends working with it
> yet or is that
I have te beginings of an implementation along the lines I describe
above. It is still not ready for review, but I have it on
lp:~kamstrup/zeitgeist/notification.
** Branch linked: lp:~kamstrup/zeitgeist/notification
--
Add event notification and subscription system
https://bugs.launchpad.net/bu
Hi,
With 0.3.0 behind us it is time to plan what to aim for in 0.3.1. I
wholeheartedly think that we should aim for a short release cycle,
maybe with releases every month or so.
Right now 0.3.1 is scheduled to 24/12 on LP and I think a deadline
around that date is good. Considering that Christmas
Until we see evidence that our DB indeed clutters up in lots of unused
URIs and whatnot (after some DeleteEvents), then I don't think the added
complexity is worth it.
A more pressing issue is to delete unused URIs after a DeleteEvents
because of privacy reasons - it's fine that we delete all even
** Changed in: zeitgeist
Milestone: 0.3.0 => 0.3.1
--
Interpretation conventions
https://bugs.launchpad.net/bugs/489262
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Status in Zeitgeist Framework: Triaged
Bu
Seif has not been able to reproduce afaik, so marking as invalid
** Changed in: zeitgeist
Status: New => Invalid
--
bug in client.py
https://bugs.launchpad.net/bugs/490110
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeis
** Changed in: zeitgeist
Milestone: 0.3.0 => 0.3.1
--
Export extensions and dataproviders into a new package
https://bugs.launchpad.net/bugs/406054
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Status in Zeit
I agree with Siegfried. It will be very convenient for apps if the
display_name of Categories (Interp. and Manif.) af translated
** Changed in: zeitgeist
Milestone: 0.3.0 => 0.3.1
--
I18N of zeitgeist
https://bugs.launchpad.net/bugs/397715
You received this bug notification because you are a
I removed this method some time before we released 0.3.0. Marking as Fix
Released
** Changed in: zeitgeist
Status: Triaged => Fix Released
--
GetHighestTimestampForActor is superfluous
https://bugs.launchpad.net/bugs/489186
You received this bug notification because you are a member of
Ze
** Changed in: zeitgeist
Status: Fix Committed => Fix Released
--
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make test/remote-test.py proper
unittests
https://bugs.launchpad.net/bugs/483550
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the re
Ok, let me jot some thoughts donw on this so we have it
* All monitoring should be done async, without polling. Ie. using signals and
callback, not sleep(5); check_drives();
* I think we can use gio.VolumeMonitor() to listen for connect/disconnect of
volumes. Then we use gio.Volume.get_uui
** Summary changed:
- What value should "actor" have?
+ What value should event.actor have?
** Changed in: zeitgeist
Assignee: (unassigned) => Mikkel Kamstrup Erlandsen (kamstrup)
** Changed in: zeitgeist
Importance: Undecided => High
** Changed in: zeitgeist
This is very related to the whole events ontology thing, and must also
be meticulously documented in our API docs. Since I am knee deep in
both, I'll assign this bug to myself.
** Changed in: zeitgeist
Assignee: (unassigned) => Mikkel Kamstrup Erlandsen (kamstrup)
--
Interp
** Summary changed:
- Origin
+ What value should subject.origin have?
** Changed in: zeitgeist
Assignee: (unassigned) => Mikkel Kamstrup Erlandsen (kamstrup)
** Changed in: zeitgeist
Importance: Undecided => High
** Changed in: zeitgeist
Status: New => Triaged
--
W
See also bug #491646
** Tags added: privacy
--
Zeitgeist should have any kind of system to protect users privacy
https://bugs.launchpad.net/bugs/447417
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Status in Zei
2009/12/3 Seif Lotfy :
> I think a 3 week period for our next release is more than enough
> As for a plan and set of features to be released we should keep it minimal.
> From the top of my head this is the TODO list:
>
> notification and subscribtions (kamstrup)
> enabling/disabling extensions usin
** Tags added: privacy
--
Delete unused stuff from DB
https://bugs.launchpad.net/bugs/491646
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Status in Zeitgeist Framework: New
Bug description:
RainCT, I used REFE
> but why "inet" and not "internet"/"online"/whatever?
Because the wind was in the west and it was a full moon when I wrote it
:-) Or perhaps I don't have a good reason.
One thing though, I don't know if we should take into consideration or
not is tunneling or VPN-like setups. So fx. some resourc
Seif; I am not sure we need an ontology here. What We really care about
is the storage ids. Zeitgeist should not care about what is what. Just
that we have "some storage medium" that can be available or not.
Going into the realm of semantics brings a lot of complexity with it,
and I think we shoul
** Changed in: zeitgeist
Assignee: (unassigned) => Mikkel Kamstrup Erlandsen (kamstrup)
--
Implement storage monitor (devices and connectivity)
https://bugs.launchpad.net/bugs/489194
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registr
** Changed in: zeitgeist
Status: Confirmed => Fix Committed
--
Add event notification and subscription system
https://bugs.launchpad.net/bugs/488967
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registrant for Zeitgeist Framework.
Status
** Summary changed:
- Interpretation conventions
+ Event Interpretations Ontology
--
Event Interpretations Ontology
https://bugs.launchpad.net/bugs/489262
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registrant for Zeitgeist Framework.
Status
redo anyway...
** Changed in: zeitgeist
Assignee: Seif Lotfy (seif) => Mikkel Kamstrup Erlandsen (kamstrup)
** Summary changed:
- Zeitgeist should have any kind of system to protect users privacy
+ Event blacklisting/Privacy mode
--
Event blacklisting/Privacy mode
https://bugs.launchpad.
I think "Physical location at which the subject resided at the moment of
interaction" is a good formulation. It is still incomplete though. We
need to define whether or not trailing slashes should be included - and
stuff like that. I'd like to keep this bug open until all of this is
thoroughly docu
In more technical engine-terms I think you are talking about defining
some more zeitgeist.datamodel.ResultTypes? I don't understand 2, but
something like 1 might be a good idea. Maybe we need to go full monty on
this:
MostPopularActor
MostRecentActor
MP Origin
MR Origin
For consistency we'd also
Public bug reported:
I think the core engine only relies on the GObject bindings in order to
get the mainloop integration needed to get DBus playing nice.
We should have a pluggable mainloop thing so that we can use the Qt
mainloop instead. On the longer term we might want to look into writing
ou
Ok. I am removing the 0.3.2 because of the disheartening comment in
http://dbus.freedesktop.org/doc/dbus-python/api/dbus-
module.html#set_default_main_loop
I can see that progress on non-native mainloops in Python DBus has not
been made since 2006/2007-ish. I'll look a bit more into this. If we ca
Siegfried, I think you need to elaborate a bit in order to make that
comment useful...
"Domain" seems to imply that it is the place where the subject is
currently located. It also strikes me as a very vague and possibly
ambiguous word here. Fx. the "domain" of an RDF property is the range
in whic
Ok. It's probably not that bad memory wise to use gobject anyway... My
testing indicates that is around 400-500kb (which is still non-
negligible, but makes the savings smaller).
--
Alternative mainloops
https://bugs.launchpad.net/bugs/493923
You received this bug notification because you are a m
> There is no need for event origin. If u want the origin of an event u look
> for the subject of the event before
The client has no rigorous way to find out which event came "before". We
can apply heuristics, but I don't like that
--
What value should subject.origin have?
https://bugs.launc
>> there are three interesting URIs to log:
>>
>> - The URL my brower window points to
>
> That's what I consider as "origin", and why I'm asking for other stuff
> to use a different name (be it "domain" or whatever else).
Ok. Let's skip the finer details of the naming as long as we agree on
the
I am not sure Tracker's goal is to store metadata about non-existing
items (fx. if I delete an image Tracker also forgets that the image had
a width of 500px, but I could be wrong). Indeed I may also download a
file to a directory Tracker is not even monitoring.
The origin URL of a file is certain
Forgot to add - great work on the branch!
--
"apriori": get most used (websites/notes/documents/etc...)
https://bugs.launchpad.net/bugs/494288
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registrant for Zeitgeist Framework.
Status in Zeitgeist
I think this is crucial. If one can not ask for related subjects withing
some specific category this feature more or less just gives apps "a shot
in the dark".
I have a few comments on the branch:
* I don't grok what the key_events.revers() call is used for, but I can
see the unit test fail if I
I don't think we should consider open/close events when calculating
these relations. That way it wont work for contacts and other non-file-
like items.
The initial step of the algorithm: "Fetch the last 7 events for this
subject uri" seems good.
The next step where you create a time range neighbo
Siegfried: Ouch. Got me :-) How about if we do ORDER count(subj_uri)
LIMIT 5 instead? It would change the ordering (quelle surprise :-)), but
I am wondering what the "correct" ordering here is? By popularity or by
recency?
--
"apriori": get most used (websites/notes/documents/etc...)
https://bugs
Seif: Fx. delta = 15 minutes, (=90ms). So you take into account all
events that happened in a 15 minute radius of the timestamp.
As far as I can see the way you do it would be meen that you consider
two events related if there are no other events in between?
I honestly don't know which approa
You are right. I think a hybrid approach would give the best results
--
"apriori": get most used (websites/notes/documents/etc...)
https://bugs.launchpad.net/bugs/494288
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registrant for Zeitgeist Frame
Public bug reported:
This bug is filed in relation to bug #495017: "AttributeError:
'NoneType' object has no attribute 'payload'"
Markus asks what to do with failed or blocked events in InsertEvents().
This is an important questions since we can't not raise an error or
simply leave the event id o
Bleh, I meant bug #495179
--
AttributeError: 'NoneType' object has no attribute 'payload'
https://bugs.launchpad.net/bugs/495017
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registrant for Zeitgeist Framework.
Status in Zeitgeist Framework: New
I opened bug #495017 to discuss the case of errors or blocked events.
Let's keep this bug on track :-)
--
AttributeError: 'NoneType' object has no attribute 'payload'
https://bugs.launchpad.net/bugs/495017
You received this bug notification because you are a member of Zeitgeist
Framework, which i
201 - 300 of 490 matches
Mail list logo
