[Zeitgeist] [Bug 486996] [NEW] testInsertGetWithoutTimestamp testcase fails
Public bug reported: Running python test/resonance-engine-test.py I get one failed testcase == FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest) -- Traceback (most recent call last): File "test/resonance-engine-test.py", line 87, in testInsertGetWithoutTimestamp self.assertTrue(ev.timestamp) AssertionError -- I would have fixed this if I were totally sure what the correct fix is. Right now the default timestamp of an event is an empty string, which is why this testcase fails. Is this the expected behaviour, and should we fix the test. Or should the default timestamp be a string containing the timestamp of object creation time? ** Affects: zeitgeist Importance: Undecided Status: New ** Changed in: zeitgeist Milestone: None => 0.3 -- 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: New Bug description: Running python test/resonance-engine-test.py I get one failed testcase == FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest) -- Traceback (most recent call last): File "test/resonance-engine-test.py", line 87, in testInsertGetWithoutTimestamp self.assertTrue(ev.timestamp) AssertionError -- I would have fixed this if I were totally sure what the correct fix is. Right now the default timestamp of an event is an empty string, which is why this testcase fails. Is this the expected behaviour, and should we fix the test. Or should the default timestamp be a string containing the timestamp of object creation time? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 486996] Re: testInsertGetWithoutTimestamp testcase fails
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 be nicer to leave it out... That said - Having the engine assign timestamps does give a slight lag on the stamps though, so that's why I prefer having the client generated. And just so that we are sure we agree; timestamps are millis since epoch, ie. int(time.time()*1000). In the Event case it needs to be a string, so wrap a str() around that. -- 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: New Bug description: Running python test/resonance-engine-test.py I get one failed testcase == FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest) -- Traceback (most recent call last): File "test/resonance-engine-test.py", line 87, in testInsertGetWithoutTimestamp self.assertTrue(ev.timestamp) AssertionError -- I would have fixed this if I were totally sure what the correct fix is. Right now the default timestamp of an event is an empty string, which is why this testcase fails. Is this the expected behaviour, and should we fix the test. Or should the default timestamp be a string containing the timestamp of object creation time? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 486996] Re: testInsertGetWithoutTimestamp testcase fails
** 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: Triaged Bug description: Running python test/resonance-engine-test.py I get one failed testcase == FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest) -- Traceback (most recent call last): File "test/resonance-engine-test.py", line 87, in testInsertGetWithoutTimestamp self.assertTrue(ev.timestamp) AssertionError -- I would have fixed this if I were totally sure what the correct fix is. Right now the default timestamp of an event is an empty string, which is why this testcase fails. Is this the expected behaviour, and should we fix the test. Or should the default timestamp be a string containing the timestamp of object creation time? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 486996] Re: testInsertGetWithoutTimestamp testcase fails
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 bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Engine. Status in Zeitgeist Engine: Triaged Bug description: Running python test/resonance-engine-test.py I get one failed testcase == FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest) -- Traceback (most recent call last): File "test/resonance-engine-test.py", line 87, in testInsertGetWithoutTimestamp self.assertTrue(ev.timestamp) AssertionError -- I would have fixed this if I were totally sure what the correct fix is. Right now the default timestamp of an event is an empty string, which is why this testcase fails. Is this the expected behaviour, and should we fix the test. Or should the default timestamp be a string containing the timestamp of object creation time? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 486996] Re: testInsertGetWithoutTimestamp testcase fails
@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 this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Engine. Status in Zeitgeist Engine: Triaged Bug description: Running python test/resonance-engine-test.py I get one failed testcase == FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest) -- Traceback (most recent call last): File "test/resonance-engine-test.py", line 87, in testInsertGetWithoutTimestamp self.assertTrue(ev.timestamp) AssertionError -- I would have fixed this if I were totally sure what the correct fix is. Right now the default timestamp of an event is an empty string, which is why this testcase fails. Is this the expected behaviour, and should we fix the test. Or should the default timestamp be a string containing the timestamp of object creation time? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 486996] Re: testInsertGetWithoutTimestamp testcase fails
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 testcase fails > https://bugs.launchpad.net/bugs/486996 > You received this bug notification because you are subscribed to The > Zeitgeist Project. > > Status in Zeitgeist Engine: Triaged > > Bug description: > Running > python test/resonance-engine-test.py > I get one failed testcase > > == > FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest) > -- > Traceback (most recent call last): > File "test/resonance-engine-test.py", line 87, in > testInsertGetWithoutTimestamp >self.assertTrue(ev.timestamp) > AssertionError > > -- > > I would have fixed this if I were totally sure what the correct fix is. > Right now the default timestamp of an event is an empty string, which is why > this testcase fails. Is this the expected behaviour, and should we fix the > test. Or should the default timestamp be a string containing the timestamp > of object creation time? > > -- 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: Triaged Bug description: Running python test/resonance-engine-test.py I get one failed testcase == FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest) -- Traceback (most recent call last): File "test/resonance-engine-test.py", line 87, in testInsertGetWithoutTimestamp self.assertTrue(ev.timestamp) AssertionError -- I would have fixed this if I were totally sure what the correct fix is. Right now the default timestamp of an event is an empty string, which is why this testcase fails. Is this the expected behaviour, and should we fix the test. Or should the default timestamp be a string containing the timestamp of object creation time? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 486996] Re: testInsertGetWithoutTimestamp testcase fails
@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 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: Triaged Bug description: Running python test/resonance-engine-test.py I get one failed testcase == FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest) -- Traceback (most recent call last): File "test/resonance-engine-test.py", line 87, in testInsertGetWithoutTimestamp self.assertTrue(ev.timestamp) AssertionError -- I would have fixed this if I were totally sure what the correct fix is. Right now the default timestamp of an event is an empty string, which is why this testcase fails. Is this the expected behaviour, and should we fix the test. Or should the default timestamp be a string containing the timestamp of object creation time? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 486996] Re: testInsertGetWithoutTimestamp testcase fails
@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 Python and using our client libs... > > -- > testInsertGetWithoutTimestamp testcase fails > https://bugs.launchpad.net/bugs/486996 > You received this bug notification because you are subscribed to The > Zeitgeist Project. > > Status in Zeitgeist Engine: Triaged > > Bug description: > Running > python test/resonance-engine-test.py > I get one failed testcase > > == > FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest) > -- > Traceback (most recent call last): > File "test/resonance-engine-test.py", line 87, in > testInsertGetWithoutTimestamp >self.assertTrue(ev.timestamp) > AssertionError > > -- > > I would have fixed this if I were totally sure what the correct fix is. > Right now the default timestamp of an event is an empty string, which is why > this testcase fails. Is this the expected behaviour, and should we fix the > test. Or should the default timestamp be a string containing the timestamp > of object creation time? > > -- 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: Triaged Bug description: Running python test/resonance-engine-test.py I get one failed testcase == FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest) -- Traceback (most recent call last): File "test/resonance-engine-test.py", line 87, in testInsertGetWithoutTimestamp self.assertTrue(ev.timestamp) AssertionError -- I would have fixed this if I were totally sure what the correct fix is. Right now the default timestamp of an event is an empty string, which is why this testcase fails. Is this the expected behaviour, and should we fix the test. Or should the default timestamp be a string containing the timestamp of object creation time? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 487297] [NEW] External dataproviders playing along the recentlyused manager
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 since for example the "text" of an mp3 is not the same as its actual title. ** Affects: zeitgeist Importance: Undecided Status: New -- External dataproviders playing along the recentlyused manager https://bugs.launchpad.net/bugs/487297 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: 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 since for example the "text" of an mp3 is not the same as its actual title. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 487321] [NEW] Origin
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 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.get_uri().rpartition("/")[0]
WHY?
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 423139] Re: Data sources should use Event and Item classes
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) => (unassigned) ** Changed in: zeitgeist Importance: Low => Undecided -- Data sources should use Event and Item classes https://bugs.launchpad.net/bugs/423139 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Engine. Status in Zeitgeist Engine: Invalid Bug description: If we have EventDict in the public module (as part of zeitgeist.dbusutils) then we should make use of it wherever applicable. Otherwise EventDict should be moved out of zeitgeist/. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 485433] Re: Dont' raise an exception when a duplicate event is detected
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: zeitgeist Assignee: (unassigned) => Seif Lotfy (seif) -- 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 for Zeitgeist Engine. Status in Zeitgeist Engine: Triaged Bug description: 19:52 thekorn: raising an exception on "Duplicate event detected" is evil 19:53 thekorn: tell me how you want recent.py to work this way 19:53 RainCT, catch this exception 19:54 thekorn: doesn't help, if I'm sending 50 event and event 10 is already there then events 11-50 won't get inserted 19:55 RainCT, ok, so the only problem is when you are importing the existing history? 19:55 thekorn: no, with the current one too, because recent.py doesn't know when the last run was 19:55 RainCT, let's open a "critical" bugreport for it 19:56 this has to be discussed and needs more thoughts 19:56 (we should workaround that in some way but still the Zeitgeist API not allowing this is a problem) ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 413782] Re: Add GetContents and GetSources to the API
** 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 because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Engine. Status in Zeitgeist Engine: Invalid Bug description: Currenty we have a GetTypes method that makes no sense since we have no such things as types anymore We should change that to GetContents and GetSources to follow our current annotation convention Also we shoudl look into our DB to check out what sources and what types are registered in our DB ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 429255] Re: sqlite error if 'application' attribute of an event is not given
** 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 in Zeitgeist Engine: Invalid Bug description: (This is a bug in the event-item-separation branch) According to the definition of an event in zeitgeist/datamodel.py the "application" attribute is optional. The attached reproducer trys to add an event with 'application' not set, it fails with the following error: Traceback (most recent call last): File "reproducer.py", line 24, in engine.insert_event(event, item) File "/home/markus/devel/gnome-zeitgeist/zeitgeist/event-item-separation/_zeitgeist/engine/querymancer_engine.py", line 425, in insert_event app_id=self._get_application_id(event["application"])) File "/home/markus/devel/gnome-zeitgeist/zeitgeist/event-item-separation/_zeitgeist/engine/querymancer.py", line 267, in add self._cursor.execute(self.INSERT(**rowspec)) sqlite3.OperationalError: no such column: None ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 426270] Re: "AttributeError: 'NoneType' object has no attribute 'execute'" if firefox is not installed
** 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 Zeitgeist Engine. Status in Zeitgeist Engine: Invalid Bug description: I get this Traceback if firefox is not installed (a history db is not found): DEBUG:root:Updating database with new Firefox History items Traceback (most recent call last): File "/home/markus/zeitgeist/trunk/zeitgeist/../zeitgeist-datahub", line 111, in _update_db_async for num, item in enumerate(self._sources_queue[0].get_items()): File "/home/markus/zeitgeist/trunk/zeitgeist/../_zeitgeist/loggers/zeitgeist_base.py", line 107, in _wrapper for n, i in enumerate(self.get_items_uncached()): File "/home/markus/zeitgeist/trunk/zeitgeist/../_zeitgeist/loggers/datasources/firefox.py", line 159, in get_items_uncached history = self.cursor.execute( AttributeError: 'NoneType' object has no attribute 'execute' ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 419867] Re: Recently Used parsing error
** 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 description: Traceback (most recent call last): File "/usr/bin/zeitgeist-datahub", line 111, in _update_db_async for num, item in enumerate(self._sources_queue[0].get_items()): File "/usr/share/zeitgeist/_zeitgeist/loggers/zeitgeist_base.py", line 107, in _wrapper for n, i in enumerate(self.get_items_uncached()): File "/usr/share/zeitgeist/_zeitgeist/loggers/datasources/recent.py", line 238, in get_items_uncached for info in self.recent_manager.get_items(): File "/usr/share/zeitgeist/_zeitgeist/loggers/datasources/_recentmanager.py", line 135, in get_items xml = minidom_parse(self.RECENTFILE) File "/usr/lib/python2.6/xml/dom/minidom.py", line 1918, in parse return expatbuilder.parse(file) File "/usr/lib/python2.6/xml/dom/expatbuilder.py", line 924, in parse result = builder.parseFile(fp) File "/usr/lib/python2.6/xml/dom/expatbuilder.py", line 207, in parseFile parser.Parse(buffer, 0) xml.parsers.expat.ExpatError: reference to invalid character number: line 1072, column 41 ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 416719] Re: forwarding added events don't include the proper bookmark status
** 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) => (unassigned) -- forwarding added events don't include the proper bookmark status https://bugs.launchpad.net/bugs/416719 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Engine. Status in Zeitgeist Engine: Won't Fix Status in Zeitgeist Engine 0.3 series: Won't Fix Bug description: before forwarding the added event we should check if the item is bookmarked in our DB since we just forward it the way we get it form the DP ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 411399] Re: Comment annotations
** 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 Zeitgeist Engine. Status in Zeitgeist Engine: Invalid Bug description: As it stands we have an item["comment"] field on our data items which is a single string. This contrasts what we actually have in the underlying datamodel where each comment is actually an annotation type. Meaning that the actual data model supports tagging comments, having events on them etc. The über simple hack would be to turn the comments into a list of strings, but that still doesn't work either - unless the strings in the list where the URIs of the comment items... Comments? (pun intended) ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 404915] Re: Add API method to change annotations of an item
** 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 Engine: Won't Fix
Status in FUSE filesystem for zeitgeist: New
Bug description:
It would be nice to have a method in the DBus API to change the annotations
(tags/bookmarked) of an item. The item should be identified by its URI.
Something like this
ChangeAnnotation("file:///boo/bar/test.dat", {"tags": ["one", "two"],
"bookmarked": False})
The 2nd argument must at least contain one item.
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 456832] Re: Firefox slowness
** 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 Importance: Wishlist => Undecided -- Firefox slowness https://bugs.launchpad.net/bugs/456832 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Engine. Status in Parental Control: New Status in Zeitgeist Engine: Invalid Bug description: Zeitgeist picks up on page changes in firefox too slowly. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 429314] Re: searching for bookmarked events is broken
** 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: Invalid Bug description: (This is a bug in the event-item-separation branch) The attached script adds a bookmarked event and a bookmarked item to the database. But FindEvents for bookmarked events returns an empty list. When you look at the database, it is also obvious that bookmarking of events is not implemented yet; we should add it, or raise an error if someone wants to add an event with 'bookmark' == True ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 407372] Re: dataprovider use content type which are not valid URIs
** 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, which is the registrant for Zeitgeist Engine. Status in Zeitgeist Engine: Invalid Bug description: the dataprovider in _zeitgesit/loggers/dataprovider use strings like "File", "Web" or "Note" as content types. Which does not match our database design spec, which claims URIs for this values. We need to change it and provide a script to convert entries in an existing DB to the new values. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 416724] Re: Insertion of same event more than once
** 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 registrant for Zeitgeist Engine. Status in Zeitgeist Engine: Invalid Status in Zeitgeist Engine 0.3 series: Invalid Bug description: We tend to insert the same event twice sometimes but very rarely. It is usually a diffrence in the float part of the timestamp! We should convert to "int" before we insert ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 392067] Re: Only one instance of the daemon and datahub should be allowed to run at once
** 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 Zeitgeist Engine. Status in Zeitgeist Engine: Fix Released Bug description: It's currently possible to run multiple instances of zeitgeist-daemon and zeitgeist-datahub at once. This shouldn't be allowed- both the daemon and the datahub should check on startup that they're not already running in a different process. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 425258] Re: origin should be a property of events, not items
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 Zeitgeist Engine: Triaged Bug description: Both http://live.gnome.org/GnomeZeitgeist/DatabaseDesign and our current implementation have "origin" as a property of items, but this makes no sense, as the origin can be different for every event and should as such be a property of it. (Further, to improve disk space usage we should save the actual value of it in the "uri" table). I'm filling this bug so that we don't remember to fix it, but please let's ignore it until we get the basic event/item separation stuff merged - most important stuff first. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 398448] Re: Compatibility with different Firefox versions (.desktop file)
** 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 Zeitgeist Engine: Invalid Bug description: The firefox datasource has "/usr/share/applications/firefox.desktop" hardcoded, but that assumption is not always valid (eg., the user may have a firefox-3.5.desktop file). ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 404914] Re: Inconsistency in FindEvents/CountEvents filter
** 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 in Zeitgeist Engine: Fix Committed Status in Zeitgeist Engine 0.2 series: Fix Released Status in Zeitgeist Engine 0.3 series: Fix Committed Bug description: Some of our filters (eg., tags, source, content, etc) take an array of different possibilities, but uri does only take a single string; this should be made more consistent (probably making the uri take an array too). Maybe we could even consider accepting everywhere either a single value or an array. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 483603] Re: Use timestamps with milliseconds granularity (was: use REAL)
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 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: Seconds are not fine-grained enough to differentiate events, so we should store the timestamps as floating-point numbers. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 420544] Re: Tomboy notes need to fill out the dict of event description
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 received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Engine. Status in Zeitgeist Engine: Won't Fix Bug description: Here is a print of Tomboy event i get from the DB: origin comment use tags bookmark 0 text Short Bio app /usr/share/applications/tomboy.desktop uri file:///home/seif/.tomboy/1d6a99a0-87fa-438a-9a85-d8fabaf94cb4.note content Note source Tomboy Notes mimetype text/plain timestamp 1251458489 icon This is not enough, since we really need the use and origin ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 416726] Re: Tomboy notes use wrong timestamps
** 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 notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Engine. Status in Zeitgeist Engine: Invalid Status in Zeitgeist Engine 0.3 series: Invalid Bug description: Tomboy events have a +1 hour offset to my current time! Small bug needs fixing! We need to push events with a unified timestamp either UTC or UTC+TZ ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 398448] Re: Compatibility with different Firefox versions (.desktop file)
** 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 in Zeitgeist Engine: Invalid Bug description: The firefox datasource has "/usr/share/applications/firefox.desktop" hardcoded, but that assumption is not always valid (eg., the user may have a firefox-3.5.desktop file). ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 487321] Re: Origin
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.get_uri().rpartition("/")[0]
WHY?
___
Mailing list: https://launchpad.net/~zeitgeist
Post to : zeitgeist@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 485433] Re: Dont' raise an exception when a duplicate event is detected
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 because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Engine. Status in Zeitgeist Engine: Triaged Bug description: 19:52 thekorn: raising an exception on "Duplicate event detected" is evil 19:53 thekorn: tell me how you want recent.py to work this way 19:53 RainCT, catch this exception 19:54 thekorn: doesn't help, if I'm sending 50 event and event 10 is already there then events 11-50 won't get inserted 19:55 RainCT, ok, so the only problem is when you are importing the existing history? 19:55 thekorn: no, with the current one too, because recent.py doesn't know when the last run was 19:55 RainCT, let's open a "critical" bugreport for it 19:56 this has to be discussed and needs more thoughts 19:56 (we should workaround that in some way but still the Zeitgeist API not allowing this is a problem) ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 483603] Re: Use timestamps with milliseconds granularity (was: use REAL)
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 notification because you are a member of Zeitgeist-Engine, which is the registrant for Zeitgeist Engine. Status in Zeitgeist Engine: New Bug description: Seconds are not fine-grained enough to differentiate events, so we should store the timestamps as floating-point numbers. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 425258] Re: origin should be a property of events, not items
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 figure out however if we want trailing slashes on origin or not... That's another issue however. ** Changed in: zeitgeist Status: Triaged => Invalid -- 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 Zeitgeist Engine: Invalid Bug description: Both http://live.gnome.org/GnomeZeitgeist/DatabaseDesign and our current implementation have "origin" as a property of items, but this makes no sense, as the origin can be different for every event and should as such be a property of it. (Further, to improve disk space usage we should save the actual value of it in the "uri" table). I'm filling this bug so that we don't remember to fix it, but please let's ignore it until we get the basic event/item separation stuff merged - most important stuff first. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
