: zeitgeist
Importance: Medium
Assignee: Markus Korn (thekorn)
Status: New
** Changed in: zeitgeist
Importance: Undecided = Medium
** Changed in: zeitgeist
Assignee: (unassigned) = Markus Korn (thekorn)
--
Define content and source types in one central place
https
** Changed in: zeitgeist
Assignee: (unassigned) = Markus Korn (thekorn)
--
Recently Used parsing error
https://bugs.launchpad.net/bugs/419867
You received this bug notification because you are a member of
Zeitgeist-Engine, which is a direct subscriber.
Status in Zeitgeist Engine: New
Bug
Can you please attach '~/.recently-used.xbel' to this bugreport. NOTE: this
file contains private data, so don't forget to switch on the privat flag for
this report.
If you feel uncomfortable to upload the whole file, please show me some lines
around line 1072 of this file.
Markus
--
ok, sorry, pushed again, sth. went wrong the first time...
--
[lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make test/remote-test.py proper
unittests
https://bugs.launchpad.net/bugs/483550
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant
merged
revno: 1299 [merge]
committer: Markus Korn thek...@gmx.de
branch nick: zeitgeist-resonance
timestamp: Tue 2009-11-17 09:11:04 +0100
message:
* turned test/remote-test.py over to a proper unittest (LP: #483550
Public bug reported:
I'm using this bug to track progress for an evolution eplugin sending
events to zeitgeist until I have a running version which is worth its
own project.
** Affects: zeitgeist
Importance: Wishlist
Assignee: Markus Korn (thekorn)
Status: In Progress
Public bug reported:
Running
python test/resonance-engine-test.py
I get one failed testcase
==
FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest)
** Changed in: zeitgeist
Status: New = Triaged
--
testInsertGetWithoutTimestamp testcase fails
https://bugs.launchpad.net/bugs/486996
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
Status in Zeitgeist Engine:
** Changed in: zeitgeist
Status: In Progress = Fix Released
--
Add engine version identifier and expose this ID over the DBus API
https://bugs.launchpad.net/bugs/462890
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist
No, this is not related to a blacklist mechanism discussed in bug 447417.
A blacklist system is on a per event basis whereas this bugreport asks for a
more global solution to manage dataprovider in general. This is esp. needed
when we have a gio dataprovider.
--
add a registry for Dataprovider
Only the Tim usecase in the description of this bugreport can be solved by a
blacklist system.
For the Tina usecase we need to find a way to apply filter on already
existing entries in the database to delete them
--
Zeitgeist should have any kind of system to protect users privacy
Public bug reported:
The old version of the engine is more verbose, has more logging
statements. For example it prints out if and how many objects are
inserted into the database. This information is useful when developing a
dataprovider to see if everything is working. We should re-add this
@Mikkel, right. So maybe it is just about putting this into an usable
UI. But this is unrelated to this bugreport.
--
Zeitgeist should have any kind of system to protect users privacy
https://bugs.launchpad.net/bugs/447417
You received this bug notification because you are a member of
** Project changed: zeitgeist = zeitgeist-dataproviders
--
create an external dataprovider for evolution
https://bugs.launchpad.net/bugs/485698
You received this bug notification because you are a member of
Zeitgeist-Engine, which is subscribed to Zeitgeist Data Providers.
Status in Zeitgeist
The attached branch has all my experiments, please see evolution/README
for a detailed report.
** Branch linked: lp:~thekorn/zeitgeist-dataproviders/evolution-
dataprovider
--
create an external dataprovider for evolution
https://bugs.launchpad.net/bugs/485698
You received this bug notification
Public bug reported:
Due to a missing pyxpcom package in ubuntu karmic the firefox extension
was hacked by files in the dbus communication process. this is VERY
inefficient. We should use XPCOM instead.
** Affects: zeitgeist-dataproviders
Importance: Undecided
Status: New
--
Right, this was my initial idea.
But maybe using mozjs-dbus is much easier, I will try it later today.
Thanks for the link.
--
firefox extension: use XPCOM instead of communicating via files
https://bugs.launchpad.net/bugs/488656
You received this bug notification because you are a member of
/python2.6/dbus/service.py, line 252, in
_method_reply_return
reply.append(signature=signature, *retval)
OverflowError: Value 889653821 out of range for UInt32
** Affects: zeitgeist
Importance: High
Assignee: Markus Korn (thekorn)
Status: In Progress
** Changed in: zeitgeist
** Changed in: zeitgeist
Status: In Progress = Fix Released
--
OverflowError in GetHighestTimestampForActor()
https://bugs.launchpad.net/bugs/489127
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Status in
Yeah, I'm ok with removing this method from the dbus API.
I would be cool if we could add a more flexible method to ZeitgeistClient, like
ZeitgeistClient.get_max_timestamp(self, actor=None,
manifestation=None, interpretation=None)
so you can not only search for the last timestamp for an actor,
** Branch linked: lp:~thekorn/+junk/test_dbus_direct_signal
--
Add event notification and subscription system
https://bugs.launchpad.net/bugs/488967
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Status in
In the attached branch I tried to put together a sample dbus service
which *should* send directed signals, but somehow it is not working as I
expect it to work.
There are two scripts, service.py which starts the service, and
client.py (0|1), the client. starting the client with argument '1' means
maybe this screencasts help to understand whyt I mean ;)
** Attachment added: out.ogv
http://launchpadlibrarian.net/36195528/out.ogv
--
Add event notification and subscription system
https://bugs.launchpad.net/bugs/488967
You received this bug notification because you are a member of
Public bug reported:
For the time_range argument, there are two ways to query for all events ever
inserted in Zeitgeist,
1.) using TimeRange.until_now(), which translates to (0,
int(time.time()*1000))
2.) (0,0)
Strictly speaking both intervals means sth. completely different, and we
Public bug reported:
Most of he metaclass magic in datamodel.py to register and define
Manifestation and Interpretation is not used anymore, we should remove
it and use much simpler (and more readable) code.
** Affects: zeitgeist
Importance: Undecided
Assignee: Markus Korn (thekorn
I'm working on fixing this bug in the attached branch
** Branch linked: lp:~thekorn/zeitgeist/simple.categories
** Changed in: zeitgeist
Status: New = In Progress
** Changed in: zeitgeist
Importance: Undecided = Low
** Changed in: zeitgeist
Milestone: None = 0.3.1
--
Make
** Changed in: zeitgeist
Status: In Progress = Fix Committed
--
Make defenition of Manifestation and Interpretation in datamodel.py simpler
https://bugs.launchpad.net/bugs/492261
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registrant
Public bug reported:
When I request all events in my database (there are about 3000 of them)
I get an operational error:
In [1]: from zeitgeist.client import ZeitgeistDBusInterface
In [2]: iface = ZeitgeistDBusInterface()
In [3]: events = iface.FindEventIds((0,0), [], 2, 5, 0)
In [4]:
** Branch linked: lp:~zeitgeist/zeitgeist/apriori
--
apriori: get most used (websites/notes/documents/etc...)
https://bugs.launchpad.net/bugs/494288
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registrant for Zeitgeist Framework.
Status in
I think I have an Idea of how to fix this bug, I will try to get some
code later today
** Changed in: zeitgeist
Assignee: (unassigned) = Markus Korn (thekorn)
--
External dataproviders playing along the recentlyused manager
https://bugs.launchpad.net/bugs/487297
You received this bug
This bug is very easy to fix, but it leads ton an important question: how do we
handle events which are not inserted (because of an error, or because of being
blocked).
Keep in mind, in our current design the clients depend on the order of items
InsertEvents returns, this allows them to map
** Changed in: zeitgeist
Milestone: None = 0.3.1
--
AttributeError: 'NoneType' object has no attribute 'payload'
https://bugs.launchpad.net/bugs/495017
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registrant for Zeitgeist Framework.
Status
I'm preparing a branch with the solution proposed by Mikkel, as this
solution has the best (making sense)/(breaking API) ratio.
** Changed in: zeitgeist
Assignee: (unassigned) = Markus Korn (thekorn)
--
What to do on failed or blocked event insertions?
https://bugs.launchpad.net/bugs
** Branch linked: lp:~thekorn/zeitgeist/zero_as_error
--
What to do on failed or blocked event insertions?
https://bugs.launchpad.net/bugs/495179
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registrant for Zeitgeist Framework.
Status in
thanks for your super fast code review.
I've changed the method name and fixed some engine-testcases (Exceptions are
not raised anymore, 0 is returned instead)
If nobody complains until lunchtime I will merge this branch into lp:zeitgeist.
This branch fixes only half of the issue, we also need a
Public bug reported:
Right now GetEvents raises a KeyError whenever any event is either not
found or blocked by an extension. As good as this solution was in case
of not found events it turns out to be bad for blocked events.
I think there are two possible solutions:
* adding a NULLEvent, a
** Changed in: zeitgeist
Status: Confirmed = Fix Committed
--
What to do on failed or blocked event insertions?
https://bugs.launchpad.net/bugs/495179
You received this bug notification because you are a member of Zeitgeist
Framework, which is the registrant for Zeitgeist Framework.
I addressed both your comments in revision 1225, thanks for the review.
--
What to do if an event is not found or blocked when calling GetEvents (or its
engine equivalent)
https://bugs.launchpad.net/bugs/495392
You received this bug notification because you are a member of Zeitgeist
Developers,
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
--
querying for events with specified actors
https://bugs.launchpad.net/bugs/496109
You received this bug notification because you are a member of Zeitgeist
Developers, which is a direct subscriber.
** Changed in: zeitgeist
Status: New = Confirmed
** Changed in: zeitgeist
Importance: Undecided = High
--
querying for events with specified actors
https://bugs.launchpad.net/bugs/496109
You received this bug notification because you are a member of Zeitgeist
Developers, which is a
revno 1222 has a remote testcase for this bug, which fails.
A testcase which does the same on engine level works just fine.
** Branch linked: lp:zeitgeist
--
querying for events with specified actors
https://bugs.launchpad.net/bugs/496109
You received this bug notification because you are a
** Changed in: zeitgeist
Assignee: Markus Korn (thekorn) = (unassigned)
--
small test
https://bugs.launchpad.net/bugs/496107
You received this bug notification because you are a member of Zeitgeist
Developers, which is the registrant for Zeitgeist Framework.
Status in Zeitgeist Framework
My last comment is kind of wrong, I adjusted the engine testcase in my
last commit to fail too
--
querying for events with specified actors
https://bugs.launchpad.net/bugs/496109
You received this bug notification because you are a member of Zeitgeist
Developers, which is a direct subscriber.
** Changed in: zeitgeist
Status: In Progress = Fix Committed
--
What to do if an event is not found or blocked when calling GetEvents (or its
engine equivalent)
https://bugs.launchpad.net/bugs/495392
You received this bug notification because you are a member of Zeitgeist
Developers,
After discussing this with Mikkel yesterday on IRC I came to the
conclusion that this bug is not an urgent one to fix, so I removed
myself as assignee.
** Changed in: zeitgeist
Assignee: Markus Korn (thekorn) = (unassigned)
--
add a registry for Dataprovider
https://bugs.launchpad.net/bugs
need the __doc__
property workaround anymore.
** Changed in: zeitgeist
Status: New = In Progress
** Changed in: zeitgeist
Assignee: (unassigned) = Markus Korn (thekorn)
--
documentation of zeitgeist
https://bugs.launchpad.net/bugs/497324
You received this bug notification because
: Markus Korn thek...@gmx.de
branch nick: trunk
timestamp: Wed 2009-12-16 20:46:46 +0100
message:
* Started restructuring the documentation (LP: #497324)
- splitted up the huge index page into smaller bits
- shpinx does now generate the documentation for Symbols
- change things
On Thu, Dec 17, 2009 at 9:49 PM, markus korn thek...@gmx.de wrote:
On Thu, Dec 17, 2009 at 9:19 PM, Mikkel Kamstrup Erlandsen
mikkel.kamst...@gmail.com wrote:
Ladys and Gents,
If we want to wrap up 0.3.1 before Christmas I believe this weekend
(19+20/12-2009) is our only shot.
Glancing
I updated lp:~thekorn/zeitgeist/negation_switch,
* it has wildcard support ('*' is used)
* added logic to Event.matches_template() and Subject.matches_template()
This updates add a new convention to zeitgeist: * in fields which
support wildcard queries must be escaped as \*
TODO:
* adding
contributors Markus Korn has not answered yet.
If Markus agrees the next logical step is to create a list of other
contributors we have that should be heard.
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Moved to the 0.3.2 milestone as implmentation details needs to be
discussed, see the discussion on the merge proposal.
** Changed in: zeitgeist
Milestone: 0.3.1 = 0.3.2
--
Using filters (text match / exclusion / etc)
https://bugs.launchpad.net/bugs/485966
You received this bug notification
Just tried to find the reasons for the failures,
* The error in 'testFindRelated' also happens in lp:zeitgeist rev 1250 (which
is before the blacklist merge)
* the other (blacklist related) failures started right after the merge (rev
1251), but they work fine in
revno: 1258
committer: Markus Korn thek...@gmx.de
branch nick: trunk
timestamp: Wed 2010-01-06 10:33:03 +0100
message:
The blacklist is running in its own DBus scope (object_path and interface
address). Using this instead
On Thu, Jan 7, 2010 at 9:07 PM, Mikkel Kamstrup Erlandsen
mikkel.kamst...@gmail.com wrote:
Hi,
In order to get our act together I propose that we go into code freeze
tomorrow at midnight (that is only trivial changes and fully approved
patches go in) and release 0.3.1 this sunday (10/1-2009).
On Thu, Jan 7, 2010 at 9:14 PM, Siegfried Gevatter rai...@ubuntu.com wrote:
Back to this, I thought I'd make sense to analyze what this means before
we do any decision. Please correct me if there's anything I got wrong!
Thanks Siegfried for this detailed explanation,
for me it is obvious that
I added a HACKING document to [0]. If someone could add information to
the Release Tasks section and check if all the other stuff makes
sense, and I did not miss anything important, we should try to get
this file into the next release.
[0]
Just found this today, dbus for JS
http://sandbox.movial.com/wiki/index.php/Browser_DBus_Bridge
--
firefox extension: use XPCOM instead of communicating via files
https://bugs.launchpad.net/bugs/488656
You received this bug notification because you are a member of Zeitgeist
Developers, which is
Blueprint changed by Markus Korn:
Whiteboard set to:
---
thekorn:
I don't get why we are talking about this over and over again. When we think we
came to a conclusion it is always a matter of time before somebody
Blueprint changed by Markus Korn:
Whiteboard changed:
---
thekorn:
I don't get why we are talking about this over and over again. When we think
we came to a conclusion it is always a matter of time before
Public bug reported:
running this command in firefox-xpcom/ stop running firefox
reproducible:
make make install firefox http://cntv.cn
but there does not seem to be a segfault etc.
** Affects: zeitgeist-dataproviders
Importance: Undecided
Status: New
--
[firefox-xpcom]
Fixed, thanks Michal
revno: 46
committer: Michal Hruby michal@gmail.com
branch nick: trunk
timestamp: Tue 2010-05-11 23:22:33 +0300
message:
Fix problems with non-ascii strings
** Changed in: zeitgeist-dataproviders
Status: New = Fix Released
** Changed in: zeitgeist-dataproviders
Assignee: (unassigned) = Markus Korn (thekorn)
--
firefox extension: use XPCOM instead of communicating via files
https://bugs.launchpad.net/bugs/488656
You received this bug
Can anybody please tell me how this is related to the dataproviders?
What das WebFav do, and how can we use this for zeitgeist, or how can zeitgeist
help webfav to do the right thing.
Thanks,
Markus
** Changed in: zeitgeist-dataproviders
Status: New = In Progress
--
Support the webfav
Hi JaVaEs,
I've never used mpd, and I have close to zero ideas how this player works. And
after looking at their wiki/source-code I've no clue how we can hook into mpd
to be notified when a song is played/skipped/stopped/...
If you or anyone else has an idea, or maybe some sample code please
** Changed in: zeitgeist-dataproviders
Status: Incomplete = Confirmed
--
add support for mpd
https://bugs.launchpad.net/bugs/579489
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Data-Sources.
Status in Zeitgeist
Hey Mikkel,
thanks you for your works, it is working fine for me.
Feel free to merge this branch into lp:zeitgeist once you thought about my
three comments ;)
Markus
=== modified file '_zeitgeist/engine/main.py'
--- _zeitgeist/engine/main.py 2010-05-03 16:32:00 +
+++
I will start hacking on this again today, a plan to split it into two
parts.
1.) I will start with negation
2.) the next step is wildcards
There are still a few open question to me:
wrt 1.)
* for which fields do we allow negation?
- Subject.{Uri, Interpretation, Manifestation, Origin,
I'll not support Subject.text for now, but make it easy to add this
field.
I mean when I look at my database for the values I've there it turns out
they are very random, like title of webpages, like Television program
of 2010-05-12, 4 - 5 p.m, negation support make close to no sense for
this
The proposal to merge lp:~thekorn/zeitgeist/negation_switch into lp:zeitgeist
has been updated.
Status: Needs review = Rejected
--
https://code.launchpad.net/~thekorn/zeitgeist/negation_switch/+merge/16416
Your team Zeitgeist Framework Team is requested to review the proposed merge of
I think I got the negation part working in
lp:~thekorn/zeitgeist/negation_support
Before a merge, this branch needs a few more tests, I hope to work on it
tomorrow early morning.
After I got this branch landed I will work on the wildcard part.
** Branch unlinked:
I think with our ontology stuff we can consider this bug as fixed.
** Changed in: zeitgeist
Status: In Progress = Fix Released
--
Event Interpretations Ontology
https://bugs.launchpad.net/bugs/489262
You received this bug notification because you are a member of Zeitgeist
Framework Team,
We implemented this kind of differentiation with the ontology branch we
landed some time ago.
** Changed in: zeitgeist
Status: Confirmed = Fix Released
** Changed in: zeitgeist
Assignee: (unassigned) = Markus Korn (thekorn)
--
Separate Interpretation/Manifestation into different
Public bug reported:
I've just added a testcase to lp:zeitgeist which shows that a template
like
template = Event.new_for_values(subject_storage=)
returns all events, instead of only all events with
subject_storage=.
There are two ways to fx this bug:
1.) implement searching for
Markus Korn has proposed merging lp:~thekorn/zeitgeist/negation_support into
lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#485966 Using filters (text match / exclusion / etc)
https://bugs.launchpad.net/bugs/485966
This branch adds negation support
Public bug reported:
Something like
event = Event.new_for_values(boo=234234)
should raise a TypeError (or ValueError) instead of creating an Event
which make no sense:
print event
Event([['', '1273824118015', '', '', ''], [], ''])
** Affects: zeitgeist
Importance: Undecided
Ok, zeitgeist is not raising a ValueError if someone tries to query on
storage, I'll let this bug open so we can implement support for this
field in the future.
revno: 1471
committer: Markus Korn thek...@gmx.de
branch nick: trunk
** Summary changed:
- Event.new_for_values() does not chec arguments
+ Event.new_for_values() does not check arguments
--
Event.new_for_values() does not check arguments
https://bugs.launchpad.net/bugs/580372
You received this bug notification because you are a member of Zeitgeist
Framework
I've started working on the wildcard part in
lp:~thekorn/zeitgeist/wildcard_support
And I'm adding another constraint: searches are case sensitive.
Please cry out loud if you think that case sensitive searches is a bad
thing.
--
Using filters (text match / exclusion / etc)
Public bug reported:
While working on the wildcard implementation I had some hard time with our
event_view view.
And I'm esp. wondering why event.actor and event.subj_mimetype are ids where
fields like event.subj_origin is already JOINed to the actual string.
Is this on purpose? shouldn't be
** Branch linked: lp:~thekorn/zeitgeist/wildcard_support
--
Using filters (text match / exclusion / etc)
https://bugs.launchpad.net/bugs/485966
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in
Markus Korn has proposed merging lp:~thekorn/zeitgeist/wildcard_support into
lp:zeitgeist.
Requested reviews:
Mikkel Kamstrup Erlandsen (kamstrup)
Zeitgeist Framework Team (zeitgeist)
This branch adds wildcard-support to some template-fields, and completes the
fix of bug 485966
--
https
*** This bug is a duplicate of bug 566898 ***
https://bugs.launchpad.net/bugs/566898
added Mikkel's work on 1.)
** Changed in: zeitgeist
Importance: Undecided = Critical
** Changed in: zeitgeist
Status: New = Confirmed
** Changed in: zeitgeist
Milestone: None = 0.3.4
** This
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
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
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
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
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
** 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
Haha, with this logic we don't need a new option at all, because / is
always top on the most used dirs list ;)
--
Tracking recent directories
https://bugs.launchpad.net/bugs/592339
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to
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
There is one reason why I don't want the daemon to always start with all
extensions found in some locations: when developing zeitgeist and
running the daemon from the branch I want to have complete control
over things which are loaded, and I also want to always run a
minimalistic version of
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
Markus Korn has proposed merging lp:~thekorn/zeitgeist/fix-595577-check-rapper
into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
#595577 Check for 'rapper' in configure (raptor-utils)
https://bugs.launchpad.net/bugs/595577
check in 'configure
** Changed in: zeitgeist
Status: Confirmed = In Progress
--
Check for 'rapper' in configure (raptor-utils)
https://bugs.launchpad.net/bugs/595577
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Status in
1 - 100 of 321 matches
Mail list logo
