** 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: Incom
** 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
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 Zeitg
** 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 Framew
** 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
--
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 i
** 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 Framew
** 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 Framew
** 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 Zei
** 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 Framewo
** 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 Zeitge
** 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
--
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 Fram
Added `make run` target to the rootlevel Makefile (LP: #660423)
[0] https://launchpad.net/zeitgeist-datahub
Have a nice day,
Markus Korn (thekorn)
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsub
Blueprint changed by Markus Korn:
Whiteboard changed:
- --- seif ---
+ --- seif 2010-10-27 10:28pm ---
Lets discuss this idea.
Do we want it as a supported extension or do we want to have in the engine.
Or do we want it as a community extension? How relevant is that to our current
work? How
Blueprint changed by Markus Korn:
Whiteboard changed:
+ --- seif ---
Lets discuss this idea.
Do we want it as a supported extension or do we want to have in the engine.
Or do we want it as a community extension? How relevant is that to our current
work? How could it help Unity and others
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 f
revno: 1623 [merge]
committer: Markus Korn
branch nick: trunk
timestamp: Mon 2010-10-25 11:48:49 +0200
message:
zeitgeist-daemon.py has now a much more readable code structure
(LP:#660415)
Also fixed the `--log-level` option, by
** 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
Hey art alexion,
I'm not sure if I completely understand the purpose of this bugreport, is it
about not logging actions on files, or are you fine with logging them, but they
should just not show up in unity.
Markus
** Changed in: zeitgeist
Status: New => Incomplete
--
can't disable rec
Ok, I've removed the logging statements you both mentioned.
> review approve
>
> I second Siegfrieds comment though. And please make sure the man page is
> clear on the subject of debug logging.
man zeitgeist-daemon says:
--log-level=LOG_LEVEL
Specifies how much information
** 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 Zeit
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
whatever namingconventions we use, we should make sure to use some kind
of log rotate, to not spam the user with tons of log files. I think
keeping the last 3 log files is enough. For our avg. user this means we
have the logs of 3 sessions.
--
Using logging output for debugging purposes
https://
revno: 1618
fixes bug(s): https://launchpad.net/bugs/660423
committer: Markus Korn
branch nick: trunk
timestamp: Fri 2010-10-15 17:36:02 +0200
message:
Added `make run` target to the rootlevel Makefile (LP: #660423
** Changed in: zeitgeist
Status: New => Fix Committed
--
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 in Zeitg
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 to the
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 subscr
Public bug reported:
Right now, whenever we get a bugreport from a user who is zeitgeist
`indirectly` (via unity, gnome-activity-journal, ...) we have to ask the
reporter to "open a terminal, run zeitgeist-daemon, do your usual stuff, get us
the logging output"
This is not optimal, as we a requ
small note to self: check if using glib.spawn_async() instead of
subprocess.Popen() to launch the datahub makes sense (is it consuming
less memory? is it easier to react on datahub failures?)
--
zeitgeist-daemon has a bad code structure
https://bugs.launchpad.net/bugs/660415
You received this bug
Seif, that's looking much better ;)
I could not find you on irc, so I did a few changes to zeitgeist-daemon.py
which came into my mind while reading the code, please contact me if you think
they don't make sense...
--
https://code.launchpad.net/~zeitgeist/zeitgeist/remove-datahub/+merge/38339
Yo
Public bug reported:
While working on some changes in zeitgeist-daemon.py I realized that testing
changes to the actual zeitgeist-daemon is hard, I always have to remember to
run make && ./zeitgeist-daemon
The `make run` target should do the right thing and simply wrap the command
above.
**
Public bug reported:
The code of zeitgeist-daemon is very hard to read, let's restructure the
code!
(This is more like a reminder for myself to work on it, but I would like
to fix it after bug #655164 has been fixed)
** Affects: zeitgeist
Importance: Undecided
Assignee: Markus
Hi Seif,
thanks for working on this. But why are you proposing branch to be merged into
lp:zeitgeist although they are obviously not working. A simple
"./zeitgeist-daemon" and a close look to zeitgeist-daemon.py will show you at
least two *very* obvious errors.
I personally don't find it motiva
Review: Approve code, unittests
Hi Seif,
thanks for working on this. It's looking good and all tests are working fine.
Feel free to do the merge.
Markus
--
https://code.launchpad.net/~zeitgeist/zeitgeist/fix-655164/+merge/38077
Your team Zeitgeist Framework Team is subscribed to branch
lp:~zeit
I did not have time yet to check if the tests make sense, but let me give you a
few comments first:
> === modified file '_zeitgeist/engine/main.py'
> --- _zeitgeist/engine/main.py 2010-09-29 08:39:32 +
> +++ _zeitgeist/engine/main.py 2010-10-10 14:57:44 +
> @@ -370,7 +370,15 @@
>
One way which just came into my mind to make things easier to understand
is to use a flag system, like
MostRecent = 0x01
LeastRecent = 0x02
MostPopular = 0x04
LeastPopular = 0x08
[...]
Events = 0x0100
Subjects = 0x0200
Actor = 0x0400
[...]
This way the ResultTypes we have right now can be written
Having such ResultTypes sounds reasonable to me, but let's ignore the
implementation details for now, and think about the `Support more ResultType`
topic a bit more:
This bugreport made me realize that the ResultType system as we have it right
now does not scale very well. Right now we have 15 d
** Description changed:
I am in discussion with the Software Center team and it seems like they are
growing fond of Zeitgeist.
There is a feature in their queue that they would like to implement and where
Zeitgeist can make it happen:
- Software Center wants to suggest applications to be i
I've made some tests tonight, on an activitylog with 18k random web history
events.
The in memory size of the daemon is about 7MiB on startup.
After running
FindEvents(TimeRange.until_now(), [],StorageState.Any, 0,1)
(same query is used by sezen *over and over again*)
the daemon's memory consump
As far as I remember, the main reason why we dropped this iterator thing being
part of our API redisign efforts a year ago was that there is no easy (and
performant) way to do batched database queries. The problem is: we don't have a
'stable' order of events, just think of a query which returns
** Changed in: zeitgeist
Status: In Progress => Fix Committed
--
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 Zeit
Once this fix has landed, I see even ways to improve time based queries
if they are not using the cornercase "complete TimeRange", but we
shouldn't take the second step before the first one...
--
Make timestamp related queries faster
https://bugs.launchpad.net/bugs/650930
You received this bug no
** Attachment added: "search_application_test.py"
https://bugs.edge.launchpad.net/bugs/650930/+attachment/1652420/+files/search_application_test.py
** Changed in: zeitgeist
Status: New => In Progress
** Changed in: zeitgeist
Assignee: (unassigned) => Mark
this time to
---> MostPopularActor: get len(ids)=6 using .find_eventids() in 0.069161s
** Affects: zeitgeist
Importance: Undecided
Assignee: Markus Korn (thekorn)
Status: In Progress
--
Make timestamp related queries faster
https://bugs.launchpad.net/bugs/650930
You received this
Markus Korn has proposed merging
lp:~thekorn/zeitgeist/fix-650930-opt-complete-timerange into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#650930 Make timestamp related queries faster
https://bugs.launchpad.net/bugs/650930
If FindEvents-queries are
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
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(
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/64
I'm removing the attached branch, since the initial issue is not fixed
by this changes (maybe indirectly=
** Branch unlinked: lp:~seif/zeitgeist/fix-641968
** Changed in: zeitgeist
Status: In Progress => Confirmed
--
querying on LeastRecentActor and MostRecentActor for a certain subject_
New version of the test script, run this script in lp:zeitgeist and in
the attached branch, compare the last line of the output, the attached
branch should be about 8-10% faster
** Attachment added: "glob-index-test_v2.py"
https://bugs.edge.launchpad.net/zeitgeist/+bug/641198/+attachment/16216
Markus Korn has proposed merging
lp:~thekorn/zeitgeist/fix-634740-634744-testrunner-improvements into
lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#634740 explicitly define on a per testcase basis which extension needs to be
loaded
https
** Branch linked: lp:~thekorn/zeitgeist/fix-634740-634744-testrunner-
improvements
--
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
** Branch linked: lp:~thekorn/zeitgeist/fix-634740-634744-testrunner-
improvements
** Changed in: zeitgeist
Status: New => In Progress
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
--
test suite fails if zeitgeist is installed on the system
Markus Korn has proposed merging
lp:~thekorn/zeitgeist/fix-641198-glob-use-index into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#641198 Prefix search is not using an index
https://bugs.launchpad.net/bugs/641198
This branch is speed optimizing the
In fact we should make sure that no non-core extension ever influence
our testsuite, testing of 3rd party extensions should be done on their
side.
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
** Changed in: zeitgeist
Status: New => In Pr
I discussed this issue with Siegfried yesterday, and I would like to bring the
overall translation workflow to everybody's attention again:
* We want to make our ontology 'symbols' translatable
* logging output should not be translated
* we might need translation support for tools in tools/
*
Public bug reported:
We have to discuss how to support versions jump in the upgrade path of
our db schema, like from ("core", 0) to ("core", 2). This becomes even
more important when we reach the next version.
For me there are two solution:
1.) write 'dummy' upgrade scripts, like core_0_2.py, whi
revno: 1595
fixes bug(s): https://launchpad.net/bugs/642898
committer: Markus Korn
branch nick: trunk
timestamp: Mon 2010-09-20 09:29:32 +0200
message:
always create core schema for new databases (LP: #642898
There are two possible solutions for this issue:
1.) check if we are operating on an empty database
2.) change our upgrade function in a way that if a upgrade script is not found
for X -> Z it tries to run X -> Y -> Z
For 1.) there are two possible ways:
1.a.) check if file already exists before
for upgrades)
** Affects: zeitgeist
Importance: Critical
Assignee: Markus Korn (thekorn)
Status: In Progress
** Changed in: zeitgeist
Status: New => In Progress
** Changed in: zeitgeist
Importance: Undecided => Critical
** Changed in: zeitgeist
** Changed in: zeitgeist
Status: In Progress => Fix Committed
--
Today's updates to lp:zeitgeist broke event_view
https://bugs.launchpad.net/bugs/642803
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Sta
Hi Mikkel,
I'm sorry, number two on your list is definitely my bad. I did not know that
this "DROP VIEW [...]" line has no effect, and I also did not test my changes
on an already existing database. My changes are indeed not working as I expect
them to work.
I'll work on fixing the issue in bug
st/../_zeitgeist/engine/sql.py",
line 59, in execute
return super(UnicodeCursor, self).execute(statement, parameters)
OperationalError: no such column: subj_uri_id
** Affects: zeitgeist
Importance: Critical
Assignee: Markus Korn (thekorn)
Status: In Progress
*
** Changed in: zeitgeist
Status: In Progress => Fix Committed
--
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 Framewo
Markus Korn has proposed merging
lp:~thekorn/zeitgeist/fix-642686-eventview-add-origin-and-uri-id into
lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#642686 Add subj_uri_id and subj_origin_id columns to event_view
https://bugs.launchpad.net/bugs
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
** Changed in: zeitgeist
Status: New => In Progress
--
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
** Attachment added: "test_new_event_view.py"
https://bugs.edge.launchpad.net/bugs/642686/+attachment/1607450/+files/test_new_event_view.py
--
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
Public bug reported:
If we add subj_uri_id and subj_origin_id columns to the event_view we
could make the prefix searches about 10% faster. Combined with the
upcoming optimization of the GLOB statement it will be possible to
reduce the avg. time for this kind of queries from ~0.20s to ~0.12s.
As
The proposal to merge lp:~zeitgeist/zeitgeist/pragma-settings into lp:zeitgeist
has been updated.
Status: Needs review => Merged
--
https://code.launchpad.net/~zeitgeist/zeitgeist/pragma-settings/+merge/35833
Your team Zeitgeist Framework Team is subscribed to branch
lp:~zeitgeist/zeitgeist
** Attachment added: "reproducer.py"
https://bugs.edge.launchpad.net/bugs/641968/+attachment/1601980/+files/reproducer.py
--
querying on LeastRecentActor for a certain subject_uri is not working
https://bugs.launchpad.net/bugs/641968
You received this bug notification because you are a membe
Public bug reported:
Scenario: I would like to know which actor touched a file with
uri="home/boo" least recently.
This query should do the job:
>>> template = Event.new_for_values(subject_uri="home/boo")
>>> ids = engine.find_eventids(TimeRange.always(), [template, ],
>>> StorageState.Any, 0, R
Hi Manish,
I don't think this is a good idea. Take your second scenario as an example, in
this case the output would contain 13 ids, which makes the logging output hard
to read.
If you want to get notified if (and which events) get inserted you can always
write a tiny Monitor you can connect to
I've another question: doesn't this change justify a boost of our db scheme
version?
--
https://code.launchpad.net/~zeitgeist/zeitgeist/pragma-settings/+merge/35833
Your team Zeitgeist Framework Team is requested to review the proposed merge of
lp:~zeitgeist/zeitgeist/pragma-settings into lp:zei
** Changed in: zeitgeist
Status: In Progress => Fix Committed
--
ZeitgeistEngine.__init__(): statement to get last row id is not using the index
https://bugs.launchpad.net/bugs/641100
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscrib
Mikkel, thanks for doing the review,
yes, the case of an empty db is covered by our unittests and everything works
just fine.
(
MIN/MAX always return sth. even if the table it's operating on is empty
In [7]: con = sqlite3.connect(":memory:")
In [8]: con.execute("CREATE TABLE boo(x)")
Out[8]:
** Attachment added: "glob-index-test.py"
https://bugs.edge.launchpad.net/bugs/641198/+attachment/1597664/+files/glob-index-test.py
** Changed in: zeitgeist
Status: New => In Progress
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
--
for ascii chars, but as we support
unicode esp. testing seems to be a bit tricky
** Affects: zeitgeist
Importance: Undecided
Assignee: Markus Korn (thekorn)
Status: In Progress
--
Prefix search is not using an index
https://bugs.launchpad.net/bugs/641198
You received this bug noti
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
** Changed in: zeitgeist
Status: New => In Progress
--
ZeitgeistEngine.__init__(): statement to get last row id is not using the index
https://bugs.launchpad.net/bugs/641100
You received this bug notifi
Markus Korn has proposed merging
lp:~thekorn/zeitgeist/fix-641100-min-max-use-index into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#641100 ZeitgeistEngine.__init__(): statement to get last row id is not using
the index
https://bugs.launchpad.net
** Attachment added: "min-max-test.py"
https://bugs.edge.launchpad.net/bugs/641100/+attachment/1597228/+files/min-max-test.py
--
ZeitgeistEngine.__init__(): statement to get last row id is not using the index
https://bugs.launchpad.net/bugs/641100
You received this bug notification because y
Public bug reported:
The attached script is creating a log with ~49k events.
In the constructor of ZeitgeistEngine we need to search for the minimum and
maximum event id. In the script I'm doing two different ways of getting these
values:
Our current query:
SELECT MIN(id), MAX(id) FROM event
-
Seif, I agree with you, reducing .commit() calls is a good idea, and as far as
I can see it's safe to remove the .commit() calls in _insert_event, given that
we never call _insert_event directly, .insert_events() is the way to go. And it
is always guaranteed that the single .commit() in insert_e
Seif, before making inserts faster I would like to understand why they
are so slow right now. The last step should be to actually add some
PRAGMA optimizations, which have, as you already mentioned some
downsides.
In order to get a better picture of what's going on, can you please try to get
some
Review: Disapprove
Seif,
before experimenting with some weird PRAGMA settings I would like to discuss
this more with the whole team, let's move discussions to the bugreport.
--
https://code.launchpad.net/~zeitgeist/zeitgeist/sqlite-insert-improvements/+merge/35701
Your team Zeitgeist Framework Te
revno: 1581 [merge]
fixes bug(s): https://launchpad.net/bugs/634055
committer: Markus Korn
branch nick: trunk
timestamp: Thu 2010-09-16 10:19:58 +0200
message:
Out ontology is now documented in a table format, which is a bit less
Public bug reported:
The documentation of the Symbol class is in a bad state. It is so bad that it
is currently not shown in our public API docs.
This class has not docstring, and has a few (important) undocumented method, we
should fix this.
Also we should remove the __doc__ property. This ugly
Markus Korn has proposed merging lp:~thekorn/zeitgeist/handle-SIGHUP into
lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Added a way to shutdown the zeitgeist-daemon in a clean way by sending a SIGHUP
signal to the process (as described in [0])
[0] http
I'm not sure, but maybe the queries are more readable if we replace '?' by the
actual values:
=== modified file '_zeitgeist/engine/sql.py'
--- _zeitgeist/engine/sql.py2010-09-13 20:55:00 +
+++ _zeitgeist/engine/sql.py2010-09-14 07:40:46 +
@@ -38,9 +38,11 @@
def explain_query(c
Review: Approve
Looks good, and it does not have to be perfect as it is for internal use only,
but I'd like to avoid the 'print' statement and put it in a logging statement.
This way it would be possible to redirect logging output of the 'zeitgeist.sql'
domain to some file etc.
Proposed diff:
Markus Korn has proposed merging
lp:~thekorn/zeitgeist-extensions/geolocation-splitup into
lp:zeitgeist-extensions.
Requested reviews:
Zeitgeist Extensions (zeitgeist-extensions)
This branch splits the geolocation extension into two parts, the logic which
defines the interface and the db
** Changed in: zeitgeist
Status: New => In Progress
** Changed in: zeitgeist
Importance: Undecided => Wishlist
** Changed in: zeitgeist
Assignee: (unassigned) => Markus Korn (thekorn)
** Changed in: zeitgeist
Milestone: None => 0.6
** Changed in: zeitgeist
Mi
Markus Korn has proposed merging lp:~thekorn/zeitgeist/fix-634055-ontology-docs
into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Out ontology is now documented in a table format, which is a bit less pythonic
than our old format and should be more readable (LP
revno: 1578 [merge]
fixes bug(s): https://launchpad.net/bugs/628678
committer: Markus Korn
branch nick: trunk
timestamp: Fri 2010-09-10 10:16:13 +0200
message:
Added information about the bug triaging process within zeitgeist to the
** Changed in: zeitgeist
Status: Confirmed => In Progress
** Changed in: zeitgeist
Assignee: Zeitgeist Framework Team (zeitgeist) => Markus Korn (thekorn)
** Changed in: zeitgeist
Milestone: 0.5.1 => 0.6
** Changed in: zeitgeist
Status: In Progress => F
Public bug reported:
Today I tried to run our test suite on a system which has zeitgeist
installed and running (maverick netbook edition). The test suite fails
with a lot of errors because it was unable to kill the running daemon
instance.
We should make sure to run our tests on its own private d
Public bug reported:
Right now we load all available extensions in our test runs. So if someone as a
random (experimental) extension in ~/.local/share/zeitgeist/extensions which
fails all our remote and engine testcases fail too.
As we have no influence on the installed extensions on the users s
Just a teaser of what I'm working on right now
** Attachment added: "onto_doc.png"
https://bugs.edge.launchpad.net/zeitgeist/+bug/634055/+attachment/1560940/+files/onto_doc.png
--
documentation of our ontology is hardly readable
https://bugs.launchpad.net/bugs/634055
You received this bug no
Public bug reported:
I just figured that the part of [0] where we list the interpretations and
manifestations is hardly readable, esp. for people with no python background.
Also it is not obvious at the first glance that these symbols have a certain
structure.
I think if we could make the docum
thanks xof32,
that's exactly what I'm expecting, but unfortunatly it doesn't help me to
understand what's going wrong.
Can I ask you for another output again? - what does
python -c "import time; print time.mktime(time.gmtime(0))"
return?
Also can you please confirm that zeitgeist-daemon still
101 - 200 of 424 matches
Mail list logo
