Yeah. We had a discussion about this at the hackfest and everyone agreed
that origin must be a property of the subject(s). So the meaning og
origin is "where does the subject come from?". For files it is the
parent folder. For websites it is the root URL (eg. http://youtube.com).
We do need to fig
Yes. Plugins *must* send the timestamps in millis since the Epoch. If
apps only use second granularity then we will have three zeroes in the
end of the timestamps.
--
Use timestamps with milliseconds granularity (was: use REAL)
https://bugs.launchpad.net/bugs/483603
You received this bug notifica
I'll do this tonight, and update the unit tests accordingly
** Changed in: zeitgeist
Assignee: Seif Lotfy (seif) => Mikkel Kamstrup Erlandsen (kamstrup)
--
Dont' raise an exception when a duplicate event is detected
https://bugs.launchpad.net/bugs/485433
You received this bug notification b
WHY NOT?
--
Origin
https://bugs.launchpad.net/bugs/487321
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
Status in Zeitgeist Engine: New
Bug description:
>> + origin =
>> info.
** Changed in: zeitgeist
Importance: Low => Undecided
--
Compatibility with different Firefox versions (.desktop file)
https://bugs.launchpad.net/bugs/398448
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
Status i
** Changed in: zeitgeist/0.3
Status: Confirmed => Invalid
** Changed in: zeitgeist/0.3
Milestone: 0.3.0 => None
** Changed in: zeitgeist/0.3
Importance: Medium => Undecided
--
Tomboy notes use wrong timestamps
https://bugs.launchpad.net/bugs/416726
You received this bug notificati
I intend to push out a new tomboy plugin that because of the 0.3 change will be
facing different issues
thus i deem thee invalid
** Changed in: zeitgeist
Status: New => Won't Fix
--
Tomboy notes need to fill out the dict of event description
https://bugs.launchpad.net/bugs/420544
You rec
I am a bit confused! Most plugins will send in seconds i think! I doubt they
will send in milliseconds.
Does this mean we will have to convert each entry we get in seconds into
milliseconds?
--
Use timestamps with milliseconds granularity (was: use REAL)
https://bugs.launchpad.net/bugs/483603
** Changed in: zeitgeist/0.3
Status: In Progress => Fix Committed
--
Inconsistency in FindEvents/CountEvents filter
https://bugs.launchpad.net/bugs/404914
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
Status
** Changed in: zeitgeist
Status: New => Invalid
--
Compatibility with different Firefox versions (.desktop file)
https://bugs.launchpad.net/bugs/398448
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
Status in
Uhm sounds like we will stay with origin belonging to the subject :P
--
origin should be a property of events, not items
https://bugs.launchpad.net/bugs/425258
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
Status in
** Changed in: zeitgeist
Status: In Progress => Fix Released
--
Only one instance of the daemon and datahub should be allowed to run at once
https://bugs.launchpad.net/bugs/392067
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Z
** Changed in: zeitgeist/0.3
Status: New => Triaged
** Changed in: zeitgeist/0.3
Status: Triaged => Invalid
--
Insertion of same event more than once
https://bugs.launchpad.net/bugs/416724
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the
** Changed in: zeitgeist
Status: Confirmed => Invalid
** Changed in: zeitgeist
Milestone: 0.3.0 => None
--
dataprovider use content type which are not valid URIs
https://bugs.launchpad.net/bugs/407372
You received this bug notification because you are a member of
Zeitgeist-Engine, wh
** Changed in: zeitgeist
Status: New => Invalid
--
searching for bookmarked events is broken
https://bugs.launchpad.net/bugs/429314
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
Status in Zeitgeist Engine: In
** Changed in: parental-control
Status: New => Fix Released
** Changed in: parental-control
Status: Fix Released => New
** Changed in: zeitgeist
Status: New => Fix Released
** Changed in: zeitgeist
Status: Fix Released => Invalid
** Changed in: zeitgeist
Importanc
** Changed in: zeitgeist
Status: New => Won't Fix
--
Add API method to change annotations of an item
https://bugs.launchpad.net/bugs/404915
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
Status in Zeitgeist En
** Changed in: zeitgeist
Status: New => Won't Fix
** Changed in: zeitgeist
Status: Won't Fix => Invalid
--
Comment annotations
https://bugs.launchpad.net/bugs/411399
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgei
** Changed in: zeitgeist/0.3
Status: New => Won't Fix
** Changed in: zeitgeist
Importance: Medium => Undecided
** Changed in: zeitgeist
Status: Confirmed => Won't Fix
** Changed in: zeitgeist
Milestone: 0.3.0 => None
** Changed in: zeitgeist
Assignee: Seif Lotfy (seif)
** Changed in: zeitgeist
Status: New => Fix Released
--
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: Fix Released
Bug descripti
** Changed in: zeitgeist
Status: New => Invalid
--
"AttributeError: 'NoneType' object has no attribute 'execute'" if firefox is
not installed
https://bugs.launchpad.net/bugs/426270
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for
** Changed in: zeitgeist
Status: New => Invalid
--
sqlite error if 'application' attribute of an event is not given
https://bugs.launchpad.net/bugs/429255
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.
Status
** Changed in: zeitgeist
Status: Confirmed => Invalid
** Changed in: zeitgeist
Importance: High => Undecided
** Changed in: zeitgeist
Milestone: 0.3.0 => None
--
Add GetContents and GetSources to the API
https://bugs.launchpad.net/bugs/413782
You received this bug notification bec
OK so what is the status on this bug! Shal lwe just return the id of the
event that is already inserted?
** Changed in: zeitgeist
Importance: Critical => Medium
** Changed in: zeitgeist
Importance: Medium => Critical
** Changed in: zeitgeist
Status: New => Triaged
** Changed in: ze
I don' see us using this anymore since we only have one DP "recently used"
Everything else will be in form of external DP
** Changed in: zeitgeist
Status: In Progress => Invalid
** Changed in: zeitgeist
Milestone: 0.3.0 => None
** Changed in: zeitgeist
Assignee: Seif Lotfy (seif
Public bug reported:
>> + origin =
info.get_uri().rpartition("/")[0]
WHY?
** Affects: zeitgeist
Importance: Undecided
Status: New
** Changed in: zeitgeist
Milestone: None => 0.3.0
--
Origin
https://bugs.launchpad.net/bugs/487321
You rece
Public bug reported:
Recently used manager can log a bunch of stuff now. However since we
want to start pushing people to use external dataproviders we should
ship the gedit and the totem plugin with 0.3, and ignore all events in
recentlyused where the actors ist gedit or totem. We gain from that
@Mikkel: OK I get ur point :)
2009/11/23 Mikkel Kamstrup Erlandsen
> @Seif: I wouldn't have to care about the timestamp format when sending
> events if my app doesn't need high precision timing. Just create the
> Event instance and send it along. Recall that not all apps will be
> written in Pyt
@Seif: I wouldn't have to care about the timestamp format when sending
events if my app doesn't need high precision timing. Just create the
Event instance and send it along. Recall that not all apps will be
written in Python and using our client libs...
--
testInsertGetWithoutTimestamp testcase f
which convenience
2009/11/23 Mikkel Kamstrup Erlandsen
> @Seif: I think we can allow empty timestamps for convenience. And as I
> said in comment 1 paragraph 3; we meassure time in milliseconds, hence
> timestamps are genrated with int(time.time()*1000).
>
> --
> testInsertGetWithoutTimestamp te
@Seif: I think we can allow empty timestamps for convenience. And as I
said in comment 1 paragraph 3; we meassure time in milliseconds, hence
timestamps are genrated with int(time.time()*1000).
--
testInsertGetWithoutTimestamp testcase fails
https://bugs.launchpad.net/bugs/486996
You received thi
We should not even allow empty timestamps in. But if you guys think we
should then an empty timestamp means we should generate one using
time.time() and insert it into the DB. What do u think?
--
testInsertGetWithoutTimestamp testcase fails
https://bugs.launchpad.net/bugs/486996
You received this
** 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:
I think a nice default is to use the timestamp of object creation time.
That was the idea behind the test at least, and indeed it also worked
like that at some point (where the test worked). Otoh - the engine will
use the current time as timestamp if the incoming event doesn't have
one, so it might
Public bug reported:
Running
python test/resonance-engine-test.py
I get one failed testcase
==
FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest)
35 matches
Mail list logo