You need to get the zeitgeist-datahub. You have the following options:
1) look into the ppa
2) bzr branch lp:zeitgeist-datahub
** Changed in: zeitgeist
Status: New => Invalid
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed t
Public bug reported:
zeitgeist-0.6 does not zeitgeist-datahub.
** Affects: zeitgeist
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net
So I just added a little temporary fix that I would like to see with the next
release.
Instead of zeitgeist returning nothing when requesting a time-period with a
broken event, zeitgeist now can ignore the broken event and return a list with
healthy events. The broken events can be seen in the l
Seif Lotfy has proposed merging lp:~seif/zeitgeist/catch_cache_error into
lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#598666 Invalid cache access (was: Error when trying to fetch items)
https://bugs.launchpad.net/bugs/598666
For more details, see:
h
Markus: Can you apply a fix for it and see if it somehow collides with
https://code.launchpad.net/~seif/zeitgeist/fix-false-payloads, then requests
for merge if all unit tests work.
This could take off a big chunk of code off. Good catch
--
https://code.launchpad.net/~manishsinha/zeitgeist/fix-69
How is it next to useless? We can attach payloads and retrieve them.
I fixed that issue.
https://code.launchpad.net/~seif/zeitgeist/fix-false-payloads
The method your fixing here is only used internally to create a pure event
for extensions to mess with. Yet however the actual event payload is als
While reading the python dbus docs [0] again I found out about the
"byte_array=True", this will solve all our problems immediately.
By using this switch in the "@dbus.service.method" and "@dbus.service.signal"
decorators, "ay" is not exposed as dbus.Array of dbus.Bytes anymore, but as
dbus.ByteA
Well, this means that the payload is next to useless.
It is not an issue mostly as event template comparison does not involve payloads
--
https://code.launchpad.net/~manishsinha/zeitgeist/fix-691167/+merge/43948
Your team Zeitgeist Framework Team is requested to review the proposed merge of
lp:~
It does not transform the actual event. but create a new popo event from the
dbus event.
The info is not needed and is not accessible by any1 outside the zeitgeist
process.
Thus I think its not an issue tbh.
--
https://code.launchpad.net/~manishsinha/zeitgeist/fix-691167/+merge/43948
Your team Ze
Review: Needs Information typecasting
What should be done? If cast is done to string, then we end up with
[[u'', u'1292500628312', u'', u'', u'application://foo.desktop'], [[u'', u'',
u'', u'', u'', u'', u'']], "dbus.Array([], signature=dbus.Signature('y'))"]
esp when the payload should be [] in
Seif sent me an activity.log which he managed to create by "[...]
randomly clicking in GAJ and synapse[...]". This log is broken and
results in the above mentioned KeyError.
The db has a few broken entries: http://paste.ubuntu.com/553188/
--
You received this bug notification because you are a m
11 matches
Mail list logo
