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
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
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
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
10:17 thekorn RainCT: so the bug is: COUNT(boo) 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,
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
revno: 1714
fixes bug(s): https://launchpad.net/bugs/739780
committer: Markus Korn thek...@gmx.de
branch nick: trunk
timestamp: Thu 2011-04-14 09:29:21 +0200
message:
Use glib.spawn_async() to launch the datahub instead
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 module
handle_exit()
File /usr/bin/zeitgeist-daemon, line 126, in handle_exit
interface.Quit()
File
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)
https
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.
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
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
** 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 Zeitgeist
Framework
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
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
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
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.
** 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.
https
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 reproduce
This looks *very* weird to me, I'll investigate later this week.
** Visibility changed to: Public
** Changed in: zeitgeist (Ubuntu)
Status: New = Triaged
** Also affects: zeitgeist
Importance: Undecided
Status: New
** Changed in: zeitgeist
Assignee: (unassigned) = Markus
@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
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,
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
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
** 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.
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
/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 of Zeitgeist
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
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.ByteArray.
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
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
@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
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.
--
*** 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:
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(),
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
** 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.
*** 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
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
** 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
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 =
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
** 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/683146
You
** 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.
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
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
@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
** 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
** 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
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
** 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,
** 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
** 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 column
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
** 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
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
Public bug reported:
mar...@thekorn /tmp/zeitgeist % bzr revno
1630
==
ERROR: testGetHook (engine-extension-test.TestExtensionHooks)
--
Traceback (most recent
** 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
** 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
Public bug reported:
As of today, ZeitgeistEngine.get_events([1, 1]) returns [None, Event with
id=1] instead of [Event with id=1, Event with id=1]
This worked in rev1629 but is not working in rev 1631 anymore.
** Affects: zeitgeist
Importance: High
Status: New
** Branch linked:
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
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
** 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 this bug
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 understanding
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
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:
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
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
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
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
** 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
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
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
---
** 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 timerange other than
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
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
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
** 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 are a member
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
DB upgrades not backwards compatible (even when their are)
https://bugs.launchpad.net/bugs/665607
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
Upgrade of the db schema strategy for version jumps
https://bugs.launchpad.net/bugs/643303
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
Replace old datahub with vala port
https://bugs.launchpad.net/bugs/630593
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
Support more ResultType
https://bugs.launchpad.net/bugs/655164
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
Make timestamp related queries faster
https://bugs.launchpad.net/bugs/650930
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
test suite fails if zeitgeist is installed on the system
https://bugs.launchpad.net/bugs/634744
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist
** Changed in: zeitgeist
Milestone: 0.6 = 0.7
--
Using logging output for debugging purposes
https://bugs.launchpad.net/bugs/660440
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
event_view changes requires schema upgrade
https://bugs.launchpad.net/bugs/642772
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: Fix Committed = Fix Released
--
zeitgeist-daemon.py has a bad code structure
https://bugs.launchpad.net/bugs/660415
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: Fix Committed = Fix Released
--
Add subj_uri_id and subj_origin_id columns to event_view
https://bugs.launchpad.net/bugs/642686
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
Prefix search is not using an index
https://bugs.launchpad.net/bugs/641198
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
explicitly define on a per testcase basis which extension needs to be loaded
https://bugs.launchpad.net/bugs/634740
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed
** Changed in: zeitgeist
Milestone: 0.6 = None
--
Error when trying to fetch items
https://bugs.launchpad.net/bugs/598666
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework:
** 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
** Changed in: zeitgeist
Status: In Progress = Fix Committed
--
zeitgeist-daemon.py has a bad code structure
https://bugs.launchpad.net/bugs/660415
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status
okidoki, my take on this: I would like to have some kind of tests for the
upgrade pathes, but please let's not do it like Seif tried in rev 1625.
Therefor I suggest the following, let's merge this branch without rev 1625 into
lp:zeitgeist, and then put some work into writing a testing framework
Markus Korn has proposed merging
lp:~thekorn/zeitgeist/fix-660415-improve-zeitgeist-daemon into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#660415 zeitgeist-daemon.py has a bad code structure
https://bugs.launchpad.net/bugs/660415
zeitgeist
** Branch linked: lp:~thekorn/zeitgeist/fix-660415-improve-zeitgeist-
daemon
** Changed in: zeitgeist
Status: Confirmed = In Progress
--
zeitgeist-daemon.py has a bad code structure
https://bugs.launchpad.net/bugs/660415
You received this bug notification because you are a member of
Review: Approve
All tests are running fine, zeitgeist-daemon is looking good, and it seems to
me that you managed to remove everything related to the old datahub, Good work.
--
https://code.launchpad.net/~zeitgeist/zeitgeist/remove-datahub/+merge/38339
Your team Zeitgeist Framework Team is
Markus Korn has proposed merging lp:~thekorn/zeitgeist/fix-660423-make-run into
lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#660423 add `make run` targets to rootlevel Makefile
https://bugs.launchpad.net/bugs/660423
Added `make run` target
1 - 100 of 262 matches
Mail list logo