** 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
revno: 1618
fixes bug(s): https://launchpad.net/bugs/660423
committer: Markus Korn thek...@gmx.de
branch nick: trunk
timestamp: Fri 2010-10-15 17:36:02 +0200
message:
Added `make run` target to the rootlevel Makefile (LP: #660423
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 Korn
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.
**
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
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
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
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
** 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
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
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
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
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
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
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 bug notification because
** 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) = Markus Korn (thekorn)
--
Make
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
** 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
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
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 =
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 to
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
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
** 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
https
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
revno: 1595
fixes bug(s): https://launchpad.net/bugs/642898
committer: Markus Korn thek...@gmx.de
branch nick: trunk
timestamp: Mon 2010-09-20 09:29:32 +0200
message:
always create core schema for new databases (LP: #642898
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, which
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/
*
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
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
** 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
** 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 member
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
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
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
Assignee: (unassigned) = Markus Korn
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
** 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.
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
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
** 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 member
** 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
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
** 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)
--
Prefix search
. 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 notification because you are a member of Zeitgeist
** 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
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
revno: 1581 [merge]
fixes bug(s): https://launchpad.net/bugs/634055
committer: Markus Korn thek...@gmx.de
branch nick: trunk
timestamp: Thu 2010-09-16 10:19:58 +0200
message:
Out ontology is now documented in a table format, which
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
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
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
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
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
** 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 = Fix Committed
--
Add
revno: 1578 [merge]
fixes bug(s): https://launchpad.net/bugs/628678
committer: Markus Korn thek...@gmx.de
branch nick: trunk
timestamp: Fri 2010-09-10 10:16:13 +0200
message:
Added information about the bug triaging process within
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
** 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
Milestone: 0.6
Markus Korn has proposed merging lp:~zeitgeist/zeitgeist/HACKING.bugtriaging
into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#628678 Add bugtriaging guidlines to HACKING
https://bugs.launchpad.net/bugs/628678
I started working on adding
I thought about this bug a bit last night, and I think I changed my mind a bit.
1.) yes, we should remove the python datahub from lp:zeitgeist entirely
2.) no, we should not do it ASAP, we should wait for it until ubuntu maverick
got released. Two reasons for this: a.) I doubt the vala datahub
** Changed in: zeitgeist
Milestone: 0.5.1 = 0.6
--
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 Zeitgeist Framework:
just for the record: http://www.sqlite.org/optoverview.html
** Changed in: zeitgeist
Milestone: None = 0.6
--
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
Blueprint changed by Markus Korn:
Definition Status: Approved = Obsolete
Whiteboard set to:
The entire blueprint is covered by a bugreport, no need to have an open
blueprint at all.
--
Replace current Datahub with the Vala implementation
https://blueprints.edge.launchpad.net/zeitgeist
Seif, I disagree with you. It is fine if this changes to our bugtriaging
policy lands at the very beginning of our 0.6 dev cycle.
** Changed in: zeitgeist
Milestone: 0.5.1 = 0.6
** Changed in: zeitgeist
Milestone: 0.6 = 0.5.1
--
Add bugtriaging guidlines to HACKING
Seif, we are not shipping HACKING in our release tarball, so it does not really
matter *when* changes to the HACKING document enter lp:zeitgeist.
So my idea is, let's get 0.5.1 out first, then discuss this topic further, and
once our bug triaging process is described in HACKING it takes effect.
** Changed in: zeitgeist
Status: New = Fix Released
--
Add `make doc` and `make check` targets to the rootlevel Makefile
https://bugs.launchpad.net/bugs/628661
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist
** Changed in: zeitgeist
Status: In Progress = Fix Released
--
Add mimetype and interpretation helper utils to public API
https://bugs.launchpad.net/bugs/586524
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/fix-586524-mimetypes-api
into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#586524 Add mimetype and interpretation helper utils to public API
https://bugs.launchpad.net/bugs/586524
This branch
** Changed in: zeitgeist
Status: Triaged = In Progress
--
Add mimetype and interpretation helper utils to public API
https://bugs.launchpad.net/bugs/586524
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Markus Korn has proposed merging
lp:~thekorn/zeitgeist/fix-628661-make-check-doc into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#628661 Add `make doc` and `make check` targets to the rootlevel Makefile
https://bugs.launchpad.net/bugs/628661
importance once we discussed this bug
further.
Markus
** Changed in: zeitgeist-dataproviders
Importance: Medium = Wishlist
** Changed in: zeitgeist-dataproviders
Assignee: Markus Korn (thekorn) = (unassigned)
--
firefox extension: still loging when in private mode
https://bugs.launchpad.net
Thanks Siegfried for the clarification, I think I now understand what this bug
is all about.
But let me ask you one final question: how much is this related to autotools
vs. packaging.
Is this bug about making a package which installs the zeitgeist module for all
available py version?
Or
Review: Disapprove
Sorry, big NACK from me.
It makes no sense to allow this kind of queries right now, as we have no ways
to set the storage state implemented. This is why we decided to throw an
exception.
--
https://code.launchpad.net/~zeitgeist/zeitgeist/bug580364/+merge/34141
Your team
Review: Needs Fixing
Ok, I cave in, fix the things mentioned by Mikkel, run the testsuite and if
everything goes well merge it into lp:zeitgeist (but please don't *bzr pull*)
--
https://code.launchpad.net/~zeitgeist/zeitgeist/bug580364/+merge/34141
Your team Zeitgeist Framework Team is
The proposal to merge lp:~thekorn/zeitgeist/fix.test.failures.20100826 into
lp:zeitgeist has been updated.
Description changed to:
This branch fixes the failures in our test suite we have right now.
* Event.new_for_values() does also have some optional arguments prefixed
subject_
* added
Review: Needs Fixing
--
https://code.launchpad.net/~zeitgeist/zeitgeist/datasource-properties-fix/+merge/33775
Your team Zeitgeist Framework Team is requested to review the proposed merge of
lp:~zeitgeist/zeitgeist/datasource-properties-fix into lp:zeitgeist.
Hmm, I think the main question here is: How do events for launching
applications look like?
From how I understand your description I think you want something like:
event = Event.new_from_values(
timestamp=1,
interpretation=ACCESS_EVENT,
manifestation=USER_ACTIVITY,
As I mentioned already on IRC, although I don't like the idea of having events
without a subject (because it's conceptual: something is happening, but we
don't know what) I think this is the easiest solution for the usecase of a GIO
dataprovider which sits in the middle of the application which
Public bug reported:
Michal reported a bug in the fts extension on irc today:
11:06 mhr3 second, once there's a bit more complex query, it no longer
expands stuff
11:07 mhr3 ie searching for v* and (v*) AND (()) returns different
results
11:08 mhr3 i'm now not
Public bug reported:
As reported by Michal on irc today, the fts extension is missing
negation support, it would be nice if we could add negation in queries.
** Affects: zeitgeist-extensions
Importance: Wishlist
Status: New
** Project changed: zeitgeist-dataproviders =
** Project changed: zeitgeist-dataproviders = zeitgeist-extensions
--
fts extension is not expanding stuff correctly in queries
https://bugs.launchpad.net/bugs/614284
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist
** Branch linked: lp:~zeitgeist/zeitgeist/hooks
--
Hook before event deletions missing
https://bugs.launchpad.net/bugs/604747
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist Framework:
** Branch linked: lp:~zeitgeist/zeitgeist/fix-592599-subject-AND
--
Hard to use exclusive queries
https://bugs.launchpad.net/bugs/592599
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Unity Files
Markus Korn has proposed merging lp:~zeitgeist/zeitgeist/fix-592599-subject-AND
into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#592599 Hard to use exclusive queries
https://bugs.launchpad.net/bugs/592599
This branch changes the connector
From my point of view this bug is Wont't fix as using (event-) templates for
almost everything in zeitgeist is a well discussed design decission, and
1.) we don't support *boo* queries, only boo*
2.) I don't think it makes sense to not use event_templates in blacklists
And if you *really* want
** Changed in: zeitgeist
Assignee: (unassigned) = Markus Korn (thekorn)
--
Hard to use exclusive queries
https://bugs.launchpad.net/bugs/592599
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status
I'm going to work on this bug and all its implications over this
weekend.
--
Hard to use exclusive queries
https://bugs.launchpad.net/bugs/592599
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Unity
I will read the docs and find out which macros to use to get a check for
rapper in configure.
** Changed in: zeitgeist
Assignee: (unassigned) = Markus Korn (thekorn)
--
Check for 'rapper' in configure (raptor-utils)
https://bugs.launchpad.net/bugs/595577
You received this bug notification
I agree, we can add this delete hook to extensions, but I'm not sure what this
hook should be able to do.
Is it to just notify an extension that a certain event is deleted, or is about
to be deleted? Or can this hook also block the removal of an event?
For notification purposes we have the
Public bug reported:
This Timeout error in testFindByRandomActorAndGet is reproducible
for me when running the testsuite
% test/remote-test.py -v ZeitgeistRemoteAPITest
:(
Ensure that the DataSourceRegistry extension is there. If
** Changed in: zeitgeist
Status: Fix Committed = Fix Released
--
Log DB file should be versioned
https://bugs.launchpad.net/bugs/566898
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in Zeitgeist
Hi Hans,
as Siegfried said in his comment the zeitgeist daemon is designed to start upon
request, so we don't need to autostart zeitgeist on session start.
This is why I'm setting this bug to won't fix
Markus
** Changed in: zeitgeist
Status: New = Won't Fix
--
Zeitgeist xdg autostart
Hi Conrad,
thanks for your feature request. I'm not sure if I understood your request
correctly, but can't your problem be solved by using this (pseudo-) code:
recent_dirs = [dirname($subject.uri) for $subject in
$recent_local_file_subjects]
Markus
** Changed in: zeitgeist
Status: New
Since this bug was reported we changed the way of loading the symbols
alot, and I don't think performance of loading datamodel.py is not an
issue anymore, please reopen (and attach some timings) if you disagree.
Markus
** Changed in: zeitgeist
Status: New = Won't Fix
--
[WIP
I agree with you here, the combinator for subjects should be AND, but
the one for events should stay OR - that makes the most sense.
** Changed in: zeitgeist
Status: New = Confirmed
--
Hard to use exclusive queries
https://bugs.launchpad.net/bugs/592599
You received this bug notification
Public bug reported:
This environment variables needs to be documented in the manpages of
zeitgeist-daemon
** Affects: zeitgeist
Importance: High
Assignee: Markus Korn (thekorn)
Status: New
** Changed in: zeitgeist
Milestone: None = 0.3.4
** Changed in: zeitgeist
revno: 1479
fixes bug(s): https://launchpad.net/bugs/585779
committer: Markus Korn thek...@gmx.de
branch nick: trunk
timestamp: Wed 2010-05-26 18:34:39 +0200
message:
added documentation for the ZEITGEIIST_{DEFAULT,EXTRA}_EXTENSIONS
I implemented the behaviour described by Mikkel in comment #17 in revno
1478 of lp:zeitgeist
revno: 1478
fixes bug(s): https://launchpad.net/bugs/483556
committer: Markus Korn thek...@gmx.de
branch nick: trunk
timestamp: Tue 2010-05-25
I think we agreed that this is most likely not an issue with zeitgeist, we also
changed test/scalability-test.py trying to reproduce exactly this scenario, but
the timings provided there are much lower than the timings provided here.
We agreed that this is most likely an issue in sezen's gtk
Public bug reported:
chromium is using a technology call NPAPI, which is also supported by
other browsers like Firefox or Safari. So if we manage to write such a
plugin then we get a dataprovider for other browser for free.
** Affects: zeitgeist-dataproviders
Importance: Undecided
The proposal to merge lp:~thekorn/zeitgeist/wildcard_support into lp:zeitgeist
has been updated.
Status: Approved = Needs review
--
https://code.launchpad.net/~thekorn/zeitgeist/wildcard_support/+merge/25345
Your team Zeitgeist Framework Team is requested to review the proposed merge of
This bug is fixed, the negation part as well as the wildcard part are
fixed in lp:zeitgeist
revno: 1470 [merge]
committer: Markus Korn thek...@gmx.de
branch nick: trunk
timestamp: Fri 2010-05-14 13:02:32 +0200
message:
Added negation
101 - 200 of 262 matches
Mail list logo
