It is not *very* slow, it just seems to be at bit slower than it should be.
>From reading the query plan the reason seems to be that two temp b-trees are
>created, which is *slow*
sele order from deta
-
1 0 0 SCAN TABLE event USING IND
Affected version is raptor2-utils >= 2.0.2
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/807076
Title:
raptor2 not supported
Status in Zeitgeist Framework:
Triaged
Statu
The problem is not in zeitgeist itself, but in the recent version of
raptor2-utils in ubuntu oneiric.
See http://bugs.librdf.org/mantis/view.php?id=451 for the upstream bugreport.
** Bug watch added: librdf Mantis #451
http://bugs.librdf.org/mantis/view.php?id=451
--
You received this bug no
I'm with Siegfried when it comes to add an extra encryption layer on top
of the db, basically I fail to understand why putting the db in an
encrypted filesystem is not good enough.
But what I find interesting is the idea of limiting the ability to
access the activity log to system-wide installed c
Review: Approve
14:55 < thekorn> RainCT: ACK from me, it does not look nice, but it has one
adv. over
the old approach, it is descriptive, you see which query
belongs to
which resulttype at the first glance
14:56 -!- m4n1sh [~manish@ubuntu/member/m4n1sh] has jo
I'm not a big friend of the idea to allow someone else than the daemon
itself modify config files like datasources.(pickle|json), because this
would require the daemon to watch-out for changes to all config files it
and its extensions are using.
libzeitgeist and the datahub should instead defer an
The zombie part of this issue should be already fixed in lp:zeitgeist by
using glib.spawn_async() instead of subprocess.Popen() (LP: #739780)
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launch
10:17 < thekorn> RainCT: so the bug is: COUNT() is working, but the
additional
sorting by timestamp is not?
10:18 < RainCT> thekorn: Right. So the question is if we want it to work (and
if so I'll
fix it together with a related bug)
10:19 < thekorn> RainCT: yes,
revno: 1714
fixes bug(s): https://launchpad.net/bugs/739780
committer: Markus Korn
branch nick: trunk
timestamp: Thu 2011-04-14 09:29:21 +0200
message:
Use glib.spawn_async() to launch the datahub instead of subprocess.Popen to
** Project changed: zeitgeist => zeitgeist-extensions
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/757512
Title:
DatabaseError
Status in Zeitgeist Extensions:
New
Bu
I was investigating on this bug a bit further. All Tracebacks are
looking like
Traceback (most recent call last):
File "/usr/bin/zeitgeist-daemon", line 180, in
handle_exit()
File "/usr/bin/zeitgeist-daemon", line 126, in handle_exit
interface.Quit()
File "/usr/share/zeitgeist/_zeit
The proposal to merge lp:~thekorn/zeitgeist/fix-598666-remove_cache_entry into
lp:zeitgeist has been updated.
Description changed to:
This branch adds a fix/workaround for bug 598666, where the caches are not
updated properly if one cached item gets deleted in the database.
https://bugs.launchp
Markus Korn has proposed merging
lp:~thekorn/zeitgeist/fix-598666-remove_cache_entry into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
Bug #598666 in Zeitgeist Framework: "Invalid cache access (was: Error when
trying to fetch items)&quo
The proposal to merge lp:~zeitgeist/zeitgeist/move-event into lp:zeitgeist has
been updated.
Status: Needs review => Merged
For more details, see:
https://code.launchpad.net/~zeitgeist/zeitgeist/move-event/+merge/53132
--
https://code.launchpad.net/~zeitgeist/zeitgeist/move-event/+merge/531
In order to find a way to fix this bug I would like to know from someone who is
affected by this bug
- which files/dirs get encrypted?
- esp.: are files in ~/.locale or ~/.local/zeitgeist encrypted (for example
by symlinking them into ~/.Private)
Thanks in advance,
Markus
** Changed in: zei
Hi @all,
we discussed this issue in the #zeitgeist IRC channel, our theory is: it's
related to encrypted homedirs, and that this dirs get unmounted before the
zeitgeist daemon stops. So the daemon is unable to write to $XDG_DATA_HOME.
We'll investigate further, and keep you updated.
Thanks for r
Public bug reported:
Instead of exposing the RuntimeError to our users we should simply exit
with a status !=0 and log the traceback.
** Affects: zeitgeist
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Zeitgeist
Framework Team,
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
** Changed in: zeitgeist
Status: Triaged => In Progress
** Changed in: zeitgeist-datahub
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of
Ok, now I know what's going on here http://paste.ubuntu.com/586129/
We just have to manage the case in the daemon that the datahub exists
immediately on daemon startup, because an already running datahub was found. We
can fix this in a few steps, first ist that the datahub should return an exit
I can reproduce this issue in my natty installation.
@Michal do you have an idea what's going on, maybe sth. wrong in the datahub?
** Also affects: zeitgeist-datahub
Importance: Undecided
Status: New
** Changed in: zeitgeist (Ubuntu)
Status: New => Confirmed
--
You received thi
@Everyone who is affected by this bug,
could you please update your (natty) system and check if you have at least
zeitgeist-datahub 0.7.0-0ubuntu1 installed, all these python and timezone
related issues should be fixed in the new implementation of the datahub.
Please open a new bug if you have t
assigned) => Markus Korn (thekorn)
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/738555
Title:
zeitgeist-daemon crashed with IOError in _write_to_disk(): [Errno 2]
No such file o
*** This bug is a duplicate of bug 714676 ***
https://bugs.launchpad.net/bugs/714676
** This bug has been marked a duplicate of bug 714676
zeitgeist-datahub crashed with OverflowError in
/usr/share/zeitgeist/_zeitgeist/loggers/datasources/_recentmanager.py: mktime
argument out of range
*
Hi David,
thanks for using zeitgeist, and reporting this bug.
Can you please open a terminal tell us what the output of the following command
gives you?
$ python -c "import time; print time.gmtime(0)"
this is finally a reproduction of bug 512166 which we closed because
noone was able to reproduc
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
** Changed in: zeitgeist
Status: New => Fix Committed
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Thanks for the reviews, I addressed them in my last commits to this
branch, I still need to test if the TEMP triggers are working properly.
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpa
Public bug reported:
We do not know if the testcases which time out (I currently have towo of them)
really pass, so we should not mark them as such.
In newer versions of python we should use SKIP, but I guess FAILED is fine too.
Alternativly we should invest some time to find out why they time ou
Public bug reported:
As of today, I have (not sure what's going wrong here):
==
FAIL: /media/sda7/zeitgeist/fix_del_cache/test/test-engine-extension.rst
Doctest: test-engine-extension.rst
-
I've added a prototype of my idea as described in my last comment, if we want
to do it this way, we have to bump the sql-schema-version, I guess.
I'm not completely sure if this is the way to go, but given the fact that the
number of entries in the _fix_cache table should be *very* low over time
Oh yeah, of course. Indeed, good work Siegfried.
While reading the last few comments one possible fix came into my mind:
Let's maintain a (temporary) helper table called '_fix_cache' with (table_name
VARCHAR, id INTEGER) and create a 'BEFORE DELETE' trigger on each cached table
(interpretation, m
I'm going to change this branch such that we only use one xml parser, minidom
or etree, thanks Mikkel for pointing this out.
--
https://code.launchpad.net/~thekorn/zeitgeist/dbus-inspect-properties/+merge/46890
Your team Zeitgeist Framework Team is requested to review the proposed merge of
lp:~t
** Branch linked: lp:~thekorn/zeitgeist/dbus-inspect-properties
** Changed in: zeitgeist
Status: New => In Progress
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/70493
Markus Korn has proposed merging lp:~thekorn/zeitgeist/dbus-inspect-properties
into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
For more details, see:
https://code.launchpad.net/~thekorn/zeitgeist/dbus-inspect-properties/+merge/46890
* Changed dbus introspection
I *feel* that our solution could look much simpler than the one from aptdaemon,
Let me just try and see how this can be implemented, we can mark this bug as
won't fix laterone if it turns out to be too complex, slow or hackish compared
to the gain.
--
You received this bug notification because
/main/view/head:/aptdaemon/core.py#L150
** Affects: zeitgeist
Importance: Undecided
Assignee: Markus Korn (thekorn)
Status: New
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
--
You received this bug notification because you are a member
** Changed in: zeitgeist/0.7
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/672965
Title:
find_event() queries with timerange oth
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
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
@Siegfried, how do you want to identify a template in the collection of
all templates, for example, what do you propose as an argument for the
RemoveTemplate() method?
Do you want automatically generated identifier (e.g. auto-integer-id,
maybe in combination with sender string)? or do you have a s
My first idea related to RegEx based matches was that I thought we need
something very powerful there. But maybe I'm wrong, So I'm happy to
change my proposal there and only allow prefix-search and negation. And
if we need something more powerful later on we can always change it.
--
You received
Please let me explain how I see the whole 'identifier' story:
I don't think we need a identifier which tells us which client set an certain
blacklist, simply because the client which sets a blacklist might not be
related to the actual purpose of this blacklist, let me give you an example:
A cale
After re-reading this bugreport, the discussion it includes and the merge
proposal, I'm still not confident that the API which is proposed here is good
enough. This is why I started working on a blacklist API spec.
It is still work in progress, and I'm not sure if this points in the right
direct
Review: Needs Information
Siegfried, you added an additional handler for SIGTERM. Can you please
elaborate when we receive such kind of signals. I mean we clearly documented
SIGHUB as a tool for distributors, and I would like to see the same
documentation for SIGTERM too.
--
https://code.launch
*** This bug is a duplicate of bug 598666 ***
https://bugs.launchpad.net/bugs/598666
Ok, my concern is: this script only uses one manifestation and one
interpretation, so dict lookup and sql query (including sqlite's internal
caching) might have the same speed.
What I'm curious to know is: i
*** This bug is a duplicate of bug 598666 ***
https://bugs.launchpad.net/bugs/598666
@Siegfried, what exactly are you benchmarking here? Eg. how many
different (relevant) values are you using? How do the graphs look if you
have some hundred different actors and mimetypes and a wide range of
us
Public bug reported:
I was wondering today why the timings for inserting events when running
our testsuite (or my benchmark scripts) are looking much better than the
timings in a 'real' daemon instance.
Some Data:
* inserting 500 events at once in my benchmarks: ~0.09 sec
* inserting the same
** Attachment added: "test_insert_events.py"
https://bugs.edge.launchpad.net/bugs/695311/+attachment/1778807/+files/test_insert_events.py
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launc
Public bug reported:
I'm talking about
def _register_data_source_python_api(self, *args):
mainloop = gobject.MainLoop()
self.client.register_data_source(*args,
reply_handler=lambda: mainloop.quit(),
error_hand
revno: 1650
fixes bug(s): https://launchpad.net/bugs/693861
committer: Markus Korn
branch nick: trunk
timestamp: Sun 2010-12-26 10:18:11 +0100
message:
* added a read-only DBus property "extensions" to org.gnome.zeitgeist.L
Okidoki, thanks for the example - what we are doing in
_zeitgeist.engine.datamodel.Event.get_plain() for payloads is indeed
wrong.
Let me clearify the purpose of this method, get_plain() is designed to
change Event(template) objects in a way that they are dumpable by the
pickle module. And we are
Manish, is this (esp. the last few lines `"dbus.Array([],
signature=dbus.Signature('y'))"`) something you get somewhere with real
code (if so, please attach a minimal reproducer) or is it *just* loud
thinking?
payload is in fact an array of bytes, as defined in the dbus signature.
You should not c
this is the set of scripts which helped me to create the benchmarks
mentioned in the attached merge proposal
** Attachment added: "cache_benchmark.tar.gz"
https://bugs.launchpad.net/zeitgeist/+bug/686732/+attachment/1759472/+files/cache_benchmark.tar.gz
--
You received this bug notification
Ohh? Is KDE (or the distro you are using) not using xdg, or why is
~/.cache not there? And if KDE uses something else for such kind of
`local log files` we should use this location instead of creating
XDG_CACHE with a big hammer.
--
You received this bug notification because you are a member of Z
Ok, first of all, thanks Harald for the input and your offer, as much as I
appreciate it I don't think we really want to move to some random other build
system.
Installing gnome-common shouldn't be a problem for anyone, because this package
has no gnome specific dependencies.
A downside of movin
completely agree, 'officially' adding a 'dbus://'-scheme would also
solve the issue of the telepathy dataprovider where we (until now) are
not sure which value to use in the actor field.
** Changed in: zeitgeist
Importance: Undecided => Wishlist
** Changed in: zeitgeist
Status: New => T
** Changed in: zeitgeist
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/680360
Title:
Zeitgeist builds man page for zeitgeist-datah
** Changed in: zeitgeist
Status: Triaged => Fix Committed
--
fix for LP: #672965 breaks returns for AJ and Synapse
https://bugs.launchpad.net/bugs/683146
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
St
** Changed in: zeitgeist
Status: New => Triaged
** Changed in: zeitgeist
Importance: Undecided => Critical
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
--
fix for LP: #672965 breaks returns for AJ and Synapse
https://bugs.launchpad.net/bugs/6
I don't agree with changing the namepsace for dbus names.
There is simply no good reason why we should make this move. After all the
"gnome" part is just a random string. And noone on KDE, Windows or whatever
platform should have a problem using this string.
Changing the name, maybe by even using
@Siegfried: yes, but it is only redundant for FindEventsStats as
FindEventIdsStats only returns ids and not events. It can't be avoided
in this particular case, as the stats field has to return *someting*.
@Michal: as we already clearified on irc, the mapping is done based on
index, so the first e
I updated my proposal at http://wiki.zeitgeist-
project.com/index.php?title=Aggregation_API
--
Add new aggregate API
https://bugs.launchpad.net/bugs/670358
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status
** Changed in: zeitgeist
Status: In Progress => Fix Committed
--
Queries for subj_uri and subj_origin are using no index
https://bugs.launchpad.net/bugs/673394
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framewor
** Changed in: zeitgeist
Status: In Progress => Fix Committed
--
Using the subj_origin column of event_view is slower than it should be
https://bugs.launchpad.net/bugs/673452
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zei
Markus Korn has proposed merging lp:~thekorn/zeitgeist/db_schema_3 into
lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#673394 Queries for subj_uri and subj_origin are using no index
https://bugs.launchpad.net/bugs/673394
#673452 Using the subj_origin
I think we don't want to merge this branch into lp:zeitgeist until we
understand the whole consequences of this change.
--
https://code.launchpad.net/~thekorn/zeitgeist/fix-672965-opt_timerange_queries/+merge/40412
Your team Zeitgeist Framework Team is requested to review the proposed merge of
l
** Changed in: zeitgeist
Status: Confirmed => Fix Committed
--
ZeitgeistEngine.get_events(rows=x) is broken
https://bugs.launchpad.net/bugs/673922
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in
Just for a reference, the last usage of the 'row' argument was removed with
https://code.launchpad.net/~zeitgeist/zeitgeist/small-find-events-optimization/+merge/34065
--
https://code.launchpad.net/~seif/zeitgeist/fix-673922/+merge/40734
Your team Zeitgeist Framework Team is requested to review t
** Branch linked: lp:~thekorn/zeitgeist/db_schema_3
** Changed in: zeitgeist
Status: Confirmed => In Progress
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
--
Queries for subj_uri and subj_origin are using no index
https://bugs.launchpad.net/bugs/
** Branch linked: lp:~thekorn/zeitgeist/db_schema_3
** Branch unlinked: lp:~thekorn/zeitgeist/faster_origin_queries
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
** Changed in: zeitgeist
Status: Triaged => In Progress
--
Using the subj_origin col
** Branch linked: lp:~thekorn/zeitgeist/db_schema_3
** Branch unlinked: lp:~thekorn/zeitgeist/db_schema_3
--
ZeitgeistEngine.get_events() returns wrong result if there are duplicates in
the ids argument
https://bugs.launchpad.net/bugs/673916
You received this bug notification because you are a
** Changed in: zeitgeist
Status: In Progress => Fix Committed
--
ZeitgeistEngine.get_events() returns wrong result if there are duplicates in
the ids argument
https://bugs.launchpad.net/bugs/673916
You received this bug notification because you are a member of Zeitgeist
Framework Team, wh
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
** Changed in: zeitgeist
Status: New => In Progress
--
ZeitgeistEngine.get_events() returns wrong result if there are duplicates in
the ids argument
https://bugs.launchpad.net/bugs/673916
You received th
Markus Korn has proposed merging
lp:~zeitgeist/zeitgeist/fix-673916-GetEvent-duplicate-id into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#673916 ZeitgeistEngine.get_events() returns wrong result if there are
duplicates in the ids argument
https
Public bug reported:
If one hands over a list of rows instead of ids to the method, get_events will
fail with a TypeError. The reason is simple: ids will become a generator (line
174) and in line 183 there is a len(ids) call, which is undefined for
generators.
This can be solved by either fixin
Public bug reported:
As of today, ZeitgeistEngine.get_events([1, 1]) returns [None, ] instead of [, ]
This worked in rev1629 but is not working in rev 1631 anymore.
** Affects: zeitgeist
Importance: High
Status: New
** Branch linked: lp:~zeitgeist/zeitgeist/fix-673916-GetEvent-dupl
As a starting-point to fix this bug I attached a branch with a testcase
--
ZeitgeistEngine.get_events() returns wrong result if there are duplicates in
the ids argument
https://bugs.launchpad.net/bugs/673916
You received this bug notification because you are a member of Zeitgeist
Framework Team,
** Changed in: zeitgeist
Status: New => Fix Committed
--
engine-extension-test.TestExtensionHooks fails in today's lp:zeitgeist
https://bugs.launchpad.net/bugs/673907
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist F
** Changed in: zeitgeist
Assignee: (unassigned) => Seif Lotfy (seif)
--
engine-extension-test.TestExtensionHooks fails in today's lp:zeitgeist
https://bugs.launchpad.net/bugs/673907
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed t
Public bug reported:
mar...@thekorn /tmp/zeitgeist % bzr revno
1630
==
ERROR: testGetHook (engine-extension-test.TestExtensionHooks)
--
Traceback (most recent c
Public bug reported:
Let me summarize what we have wrt subj_origin
1) we have a subj_origin column in the event table, which is an integer
pointing to an entry in the uri table
2) we have an index on the subj_origin column of the event table
3) we have subj_origin in event view, which is not t
Also, bug 673452
--
Slow queries: SQL indexes not used
https://bugs.launchpad.net/bugs/632363
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: Confirmed
Bug description:
THE PROBLE
Bug 673394 describes anopther class of slow queries
--
Slow queries: SQL indexes not used
https://bugs.launchpad.net/bugs/632363
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework: Con
Public bug reported:
We have a bunch of queries which are using no index and therefor are
much slower than others, this is one example:
Running: engine.find_eventids(TimeRange.always(), [], StorageState.Any, 6,
ResultType.MostRecentSubjects)
DEBUG:zeitgeist.sql:Got query:
QUERY:
SELECT DISTINCT
Public bug reported:
mar...@thekorn ~/devel/zeitgeist/trunk % grep -ri "iso_strptime.py" .
./COPYRIGHT:26:File zeitgeist/loggers/iso_strptime.py is part of wadllib, which
is
./extra/packaging/debian/copyright:20:Files: zeitgeist/loggers/iso_strptime.py
>From my understandi
Running ANALYZE after inserting the sample data and before running the
find_event queries does not change anything, for both, this branch and
lp:zeitgeist.
I must admit I don't understand why not using the timestamp index is
*significantly* faster, but it is (0.26s -> 0.07s, 0.20s -> 0.06s etc.)
** Changed in: zeitgeist
Status: New => In Progress
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
** Changed in: zeitgeist
Importance: Undecided => Low
** Changed in: zeitgeist
Milestone: None => 0.7.0
--
find_event() queries with tim
The question which came in my mind after changing the code was: does the
performance of other queries suffer from this change, so I changed the script
attached to the bug to test all ResultType
Before the change:
---> LeastPopularActor: get len(ids)=6 using .find_eventids() in 0.078450s
---> Le
Markus Korn has proposed merging
lp:~thekorn/zeitgeist/fix-672965-opt_timerange_queries into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#672965 find_event() queries with timerange other than TimeRange.always() are
slow
https://bugs.launchpad.net
** Description changed:
When running the attached script you can see that when giving a
timerange which does not start at 0 and end at maxint the queries get
- 400% slower.
-
+ 300% slower.
python sample_timerange_query.py
DEBUG:zeitgeist.sql:Got query:
QUERY:
SELECT DISTINCT id FR
I've just filed bug 672965 for one class of slow queries
--
Slow queries: SQL indexes not used
https://bugs.launchpad.net/bugs/632363
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework
** Attachment added: "sample_timerange_query.py"
https://bugs.launchpad.net/bugs/672965/+attachment/1727743/+files/sample_timerange_query.py
--
find_event() queries with timerange other than TimeRange.always() are slow
https://bugs.launchpad.net/bugs/672965
You received this bug notification
Public bug reported:
When running the attached script you can see that when giving a
timerange which does not start at 0 and end at maxint the queries get
400% slower.
python sample_timerange_query.py
DEBUG:zeitgeist.sql:Got query:
QUERY:
SELECT DISTINCT id FROM event_view GROUP BY actor ORDER B
ups, pressed 'post comment' to early, from my POV this bug is 'won't
fix'
--
dynamic loading of extensions
https://bugs.launchpad.net/bugs/670355
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgei
Restarting of zeitgeist after installation the GAJ package requires no
user action, because GAJ does the right thing (tm), in its package
install process a SIGHUB signal is send to zeitgeist, which shuts the
daemon down. - If this is not the case right now, it's a bug in the
packaging of GAJ.
And
I suggest something like:
def find_events_and_data(*find_event_arguments, datatype_const):
...
return result
result = [events, data]
datatype_const:
DATATYPE_COUNT -> result of COUNT() from within the sql-query
DATATYPE_RELATIVE_COUNT -> result of COUNT() from within the sql-
The fact that all monitors are gone when restarting zeitgeist is not an
argument, because there is not guarantee that the zeitgeist daemon will run
forever, so if you connect a monitor to the daemon, you have to handle the case
of a daemon restart/shutdown, aka reconnecting the monitors after th
** Changed in: zeitgeist-dataproviders
Assignee: (unassigned) => Markus Korn (thekorn)
** Changed in: zeitgeist-dataproviders
Status: New => Fix Committed
--
`make distcheck` fails badly
https://bugs.launchpad.net/bugs/668771
You received this bug notification because you
Changing target back to 'unity-place-files' because this bug is about a
missing toggle in the UI
** Project changed: zeitgeist => unity-place-files
--
can't disable recently used documents
https://bugs.launchpad.net/bugs/663552
You received this bug notification because you are a member of Zeitg
** Changed in: zeitgeist
Status: Fix Committed => Fix Released
--
add `make run` targets to rootlevel Makefile
https://bugs.launchpad.net/bugs/660423
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status
One part of this bug, not using lp:zeitgeist as target branch for
translations, has been fixed, but there are still some issues with i18n
in zeitgeist, as mentioned in the description and in one of my last
comments.
** Changed in: zeitgeist
Milestone: 0.6 => 0.7
--
I18N of zeitgeist
https://
1 - 100 of 424 matches
Mail list logo