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
I don't get why we need magic like ${PYTHON} at all. Isn't
/usr/bin/python always linked to the python version preferred by the
user? - so wn't fix for me too, unless there is a good reason I'm
missing.
** Changed in: zeitgeist
Status: Triaged => Incomplete
--
zeitgeist-0.2.0: using "env
** 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 F
I think this should be done with the blacklist feature i discussed in the
other bug
2009/11/25 Siegfried Gevatter
> Afaik the idea was that there should be a central place where any logger
> can be disabled. In any case, we still need this for stuff in the
> datahub (which may do logging from on
Afaik the idea was that there should be a central place where any logger
can be disabled. In any case, we still need this for stuff in the
datahub (which may do logging from online services in the future, etc).
** Changed in: zeitgeist
Importance: Undecided => Low
** Changed in: zeitgeist
Afaik the idea was that there should be a central place where any logger
can be disabled. In any case, we still need this for stuff in the
datahub (which may do logging from online services in the future, etc).
--
add a registry for Dataprovider
https://bugs.launchpad.net/bugs/462894
You received
2009/11/25 Seif Lotfy :
> Manifestation and Interpretation are part of an ontology and our own set of
> rules and conventions that should be translated by apps however not by us.
No, the public Python API exposes manifestations and interpretations
and has a user-readable name an description for e
This is a WONTFIX from my side (feature, not a bug), but I can be
convinced otherwise.
(In any case, we can't just change the files directly because then
Zeitgeist wouldn't run in-place anymore, but some little sed magic in
the Makefiles would do I guess.)
--
zeitgeist-0.2.0: using "env python"
** Changed in: zeitgeist
Status: Triaged => Fix Released
--
Update to use new logo everywhere
https://bugs.launchpad.net/bugs/483585
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
Status in Zeitgeist Framework
Most of our messages are logging and debug messages that in my opinion should
not be even translated.
Manifestation and Interpretation are part of an ontology and our own set of
rules and conventions that should be translated by apps however not by us.
Correct me if I am wrong please so we can c
There are several ways of tackling this issue:
1) Either not log events from specific apps (which is solved now) by disabling
the plugins in the applications
2) Have a little profiler as in a blacklist for home and another for work.
Those could be either actors or subjects. According to the activ
For all i can see countevents is not there anymore. The issues with
bookmarks etc is not relevant anymore.
** Changed in: zeitgeist/0.3
Status: Fix Committed => Fix Released
--
Inconsistency in FindEvents/CountEvents filter
https://bugs.launchpad.net/bugs/404914
You received this bug noti
Siegfried what is the status on this bug?
--
zeitgeist-datahub crashed with OperationalError in get_items_uncached()
https://bugs.launchpad.net/bugs/437686
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
Status in Zei
ok so this means i need to change my plugins right? Lets see how
recentlyused manager does it. This might need to be changed!
--
Use timestamps with milliseconds granularity (was: use REAL)
https://bugs.launchpad.net/bugs/483603
You received this bug notification because you are a member of
Zeitg
As far as i know this is also solved by now in GetEvents
** Changed in: zeitgeist
Status: New => Fix Released
--
Expose the item.payload column in the DBus API
https://bugs.launchpad.net/bugs/446733
You received this bug notification because you are a member of
Zeitgeist-Engine, which is
Small task for Siegfried
** Changed in: zeitgeist
Status: New => Triaged
** Changed in: zeitgeist
Importance: Undecided => Low
** Changed in: zeitgeist
Assignee: (unassigned) => Siegfried Gevatter (rainct)
** Changed in: zeitgeist
Milestone: None => 0.3.0
--
zeitgeist-0.2.0
Again redundant since our dataproviders will reside within applications
** Changed in: zeitgeist
Status: New => Invalid
--
add a registry for Dataprovider
https://bugs.launchpad.net/bugs/462894
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the r
With the exporting of the dataproviders, it is not our job anymore since
applications can deactivate their "informer".
Thus won't invalid
** Changed in: zeitgeist
Status: Confirmed => Invalid
** Changed in: zeitgeist
Milestone: 0.3.0 => None
--
DataProviders: only watch files if Dat
I think this is done for right?
--
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 Engine.
Status in Zeitgeist Engine:
I think the exclusion makes a lot of sense and i think the "!" would be
a good indicator for exclusion. Example this would be interesting if i
want to query for my last 100 events excluding those from firefox, since
firefox kinda bloats everything here. I can see myself using this a lot
later in re
Siegfried, I think you make a good case. However I don't see it
conflicting with what we have now though. Whether origin is something on
the event or the subject(s) is purely a matter of how one looks at it
now that we have a 1 to 1 mapping between events and subjects in the db.
The tricky part is
uhm other way round where the subject came from :)
2009/11/24 Siegfried Gevatter
> Seif: Thanks for your kind words.
>
> Everyone: Okay now that I'm home (wrote the previous message when
> checking mails from the phone, so that I don't forget to answer :P),
> here comes what I wanted to say.
>
>
Seif: Thanks for your kind words.
Everyone: Okay now that I'm home (wrote the previous message when
checking mails from the phone, so that I don't forget to answer :P),
here comes what I wanted to say.
As I understand it, the point for "origin" is to know where a particular
event came from. So, e
Fixed in r1158
** Changed in: zeitgeist
Status: Triaged => Fix Released
--
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.
St
Fixed in revision #1157
** Changed in: zeitgeist
Status: Triaged => Fix Released
--
Dont' raise an exception when a duplicate event is detected
https://bugs.launchpad.net/bugs/485433
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant f
WISE ASS
2009/11/24 Siegfried Gevatter
> Everyone not, I disagree with that concept of origin, but anyway, will
> write more once I´m home.
>
> --
> Siegfried-Angel Gevatter Pujals (RainCT)
> Free Software Developer 363DEAE3
>
> --
> origin should be a property of events, not items
> https
Everyone not, I disagree with that concept of origin, but anyway, will
write more once I´m home.
--
Siegfried-Angel Gevatter Pujals (RainCT)
Free Software Developer 363DEAE3
--
origin should be a property of events, not items
https://bugs.launchpad.net/bugs/425258
You received this bug no
REALLY GUYS? HERE? LOL
2009/11/24 Mikkel Kamstrup Erlandsen
> WHY NOT?
>
> --
> Origin
> https://bugs.launchpad.net/bugs/487321
> You received this bug notification because you are subscribed to The
> Zeitgeist Project.
>
> Status in Zeitgeist Engine: New
>
> Bug description:
> >> +
28 matches
Mail list logo
