Re: [Zeitgeist] Upcoming release (0.8.0)
2011/5/5 Siegfried-Angel Gevatter Pujals siegfr...@gevatter.com: - LP #691167: Changing the payload to an array of bytes (as available in Python 2.7+). That is 2.6, of course. -- Siegfried-Angel Gevatter Pujals (RainCT) Free Software Developer 363DEAE3 ___ 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] Upcoming release (0.8.0)
Hey all, Just a quick mail to mention that I'm planning to release Zeitgeist 0.8.0 Saturday night. Releases of libzeitgeist, data-sources, global-privacy (whatever it's definitive name will be) and all should follow soon, at the discretion of whoever takes the role of Master of the Tarball [0]. So, in case you have any concerns related to the upcoming release, speak now or remain silent forever. From my side, what's missing for the release is: - Implementing *CurrentUri sortings. - Adding *SubjectOrigin aliases for the old *Origin sortings (this involves getting rid of meta-classes in datamodel.py, as agreed with Markus Korn). - Fixing the MOVE_EVENT handling to only rename events with a timestamp older than that of the move event (there is more to the story -I'll file a bug related to this shortly-, but Seif defends it's not important enough to hold up the release). If some kind soul wants to fix stuff, these ones (for instance) would be nice to have fixed but don't really matter much: - LP #691167: Changing the payload to an array of bytes (as available in Python 2.7+). - LP: #772474: Somehow fixing autohell to check for rdflib in Python 2 and not Python 3 (on messed up systems where 3 is the default). Cheers, -- Siegfried-Angel Gevatter Pujals (RainCT) Free Software Developer 363DEAE3 [0] http://4.bp.blogspot.com/_w6uR1ccXoqc/TB-YWf4tslI/Bpw/VYAfEIxHZwo/s1600/dung-beetle1.jpg QOTD: «I thought of a cool concept for a fiction piece involving the whole uncertainty thing. Might write it. And by might, I mean I won't and the cat is obviously dead.» --AHMETxRock ___ 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 778140] [NEW] MOVE_EVENT handling doesn't support unsorted events for the same uri
Public bug reported: RainCT seiflotfy: the query updating current_uri on MOVE_EVENT should only change stuff with timestampmove_event_timestamp seiflotfy RainCT, true seiflotfy good catch RainCT seiflotfy: there's also another ugly case seiflotfy RainCT, do tell RainCT seiflotfy: Imagine you insert event: 0. A, 1. A, 2. A, 3. B, 4. C, 5. A. Then with timestamp between events 3 and 4 you get A-T, so now you have T, T, T, B, C, A [...] seiflotfy i see the problem seiflotfy the last A should be a T RainCT no, the last A is fine RainCT because it is a new file with the same name [...] seiflotfy yeah ok RainCT seiflotfy: now you get A-L with timestamp between 1 and 2, so it should have L, L, T, B, C, A, but since the current_uri of the first is already L you won't see it. for this it'd need to check the original URI instead of the current_uri RainCT are you with me so far? seiflotfy trying to seiflotfy RainCT, ok i cont get your last point seiflotfy A-L wont change the T seiflotfy because A has been move to T seiflotfy you can not move A again seiflotfy you need to move T seiflotfy thus its does not work RainCT yeah, but it should, because you're being told that it was moved before that seiflotfy unless you really want to you will have to look for all MOVE_EVENTS with A and figure out what A is now seiflotfy its doable RainCT so the move that happened later in time didn't affect those events, only the later ones seiflotfy RainCT, true RainCT the easy way to solve this is checking subj_id instead of subj_id_current seiflotfy RainCT, i think we should raise an exception RainCT but now when it gets really messed up is if there was even another move event before that RainCT which was already logged seiflotfy You tried to move and event after it was used in a new location seiflotfy RainCT, actually we also have the MOVE_EVENT logged seiflotfy you can then try to figrue out the patch of A RainCT yes, that's the solution seiflotfy the path seiflotfy RainCT, but i highly discourage that RainCT you can find the previos move event and set timestampprevious_move_event.timestamp seiflotfy RainCT, exactly seiflotfy i am +- 0 on that tbh seiflotfy not sure RainCT ok, I don't dislike finding the previous timestamp RainCT i'll open a bug ** Affects: zeitgeist Importance: Medium Assignee: Siegfried Gevatter (rainct) Status: Triaged -- You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. https://bugs.launchpad.net/bugs/778140 Title: MOVE_EVENT handling doesn't support unsorted events for the same uri Status in Zeitgeist Framework: Triaged Bug description: RainCT seiflotfy: the query updating current_uri on MOVE_EVENT should only change stuff with timestampmove_event_timestamp seiflotfy RainCT, true seiflotfy good catch RainCT seiflotfy: there's also another ugly case seiflotfy RainCT, do tell RainCT seiflotfy: Imagine you insert event: 0. A, 1. A, 2. A, 3. B, 4. C, 5. A. Then with timestamp between events 3 and 4 you get A-T, so now you have T, T, T, B, C, A [...] seiflotfy i see the problem seiflotfy the last A should be a T RainCT no, the last A is fine RainCT because it is a new file with the same name [...] seiflotfy yeah ok RainCT seiflotfy: now you get A-L with timestamp between 1 and 2, so it should have L, L, T, B, C, A, but since the current_uri of the first is already L you won't see it. for this it'd need to check the original URI instead of the current_uri RainCT are you with me so far? seiflotfy trying to seiflotfy RainCT, ok i cont get your last point seiflotfy A-L wont change the T seiflotfy because A has been move to T seiflotfy you can not move A again seiflotfy you need to move T seiflotfy thus its does not work RainCT yeah, but it should, because you're being told that it was moved before that seiflotfy unless you really want to you will have to look for all MOVE_EVENTS with A and figure out what A is now seiflotfy its doable RainCT so the move that happened later in time didn't affect those events, only the later ones seiflotfy RainCT, true RainCT the easy way to solve this is checking subj_id instead of subj_id_current seiflotfy RainCT, i think we should raise an exception RainCT but now when it gets really messed up is if there was even another move event before that RainCT which was already logged seiflotfy You tried to move and event after it was used in a new location seiflotfy RainCT, actually we also have the MOVE_EVENT logged seiflotfy you can then try to figrue out the patch of A RainCT yes, that's the solution seiflotfy the path seiflotfy RainCT, but i highly discourage that RainCT you can find the previos move event and set timestampprevious_move_event.timestamp seiflotfy RainCT, exactly seiflotfy i am +- 0 on that tbh seiflotfy not sure RainCT ok, I don't dislike finding the
[Zeitgeist] [Merge] lp:~seif/zeitgeist/fix-691167 into lp:zeitgeist
Seif Lotfy has proposed merging lp:~seif/zeitgeist/fix-691167 into lp:zeitgeist. Requested reviews: Zeitgeist Framework Team (zeitgeist) For more details, see: https://code.launchpad.net/~seif/zeitgeist/fix-691167/+merge/60125 Fix for 691167 -- https://code.launchpad.net/~seif/zeitgeist/fix-691167/+merge/60125 Your team Zeitgeist Framework Team is requested to review the proposed merge of lp:~seif/zeitgeist/fix-691167 into lp:zeitgeist. === modified file '_zeitgeist/engine/remote.py' --- _zeitgeist/engine/remote.py 2011-04-11 18:13:58 + +++ _zeitgeist/engine/remote.py 2011-05-05 21:42:28 + @@ -84,7 +84,7 @@ @dbus.service.method(constants.DBUS_INTERFACE, in_signature=au, out_signature=a(+constants.SIG_EVENT+), - sender_keyword=sender) + sender_keyword=sender, byte_arrays=True) def GetEvents(self, event_ids, sender): Get full event data for a set of event IDs @@ -101,11 +101,11 @@ :rtype: A list of serialized events. DBus signature a(asaasay). return self._make_events_sendable(self._engine.get_events(ids=event_ids, - sender=sender)) + sender=sender)) @dbus.service.method(constants.DBUS_INTERFACE, in_signature=(xx)a(+constants.SIG_EVENT+)a(+constants.SIG_EVENT+)uuu, - out_signature=as) + out_signature=as, byte_arrays=True) def FindRelatedUris(self, time_range, event_templates, result_event_templates, storage_state, num_events, result_type): Warning: This API is EXPERIMENTAL and is not fully supported yet. @@ -153,7 +153,8 @@ @dbus.service.method(constants.DBUS_INTERFACE, in_signature=(xx)a(+constants.SIG_EVENT+)uuu, - out_signature=au) + out_signature=au, + byte_arrays=True) def FindEventIds(self, time_range, event_templates, storage_state, num_events, result_type): Search for events matching a given set of templates and return @@ -217,7 +218,8 @@ @dbus.service.method(constants.DBUS_INTERFACE, in_signature=(xx)a(+constants.SIG_EVENT+)uuu, out_signature=a(+constants.SIG_EVENT+), - sender_keyword=sender) + sender_keyword=sender, + byte_arrays=True) def FindEvents(self, time_range, event_templates, storage_state, num_events, result_type, sender): Get events matching a given set of templates. @@ -275,7 +277,8 @@ @dbus.service.method(constants.DBUS_INTERFACE, in_signature=a(+constants.SIG_EVENT+), out_signature=au, - sender_keyword=sender) + sender_keyword=sender, + byte_arrays=True) def InsertEvents(self, events, sender): Inserts events into the log. Returns an array containing the IDs of the inserted events @@ -324,9 +327,9 @@ return event_ids @dbus.service.method(constants.DBUS_INTERFACE, - in_signature=au, - out_signature=(xx), - sender_keyword=sender) + in_signature=au, + out_signature=(xx), + sender_keyword=sender) def DeleteEvents(self, event_ids, sender): Delete a set of events from the log given their IDs @@ -339,7 +342,7 @@ # We need to check the return value, as the events could already # have been deleted before or the IDs might even have been invalid. self._notifications.notify_delete( - TimeRange(timestamps[0], timestamps[1]), event_ids) +TimeRange(timestamps[0], timestamps[1]), event_ids) if timestamps is None: # unknown event id, see doc of delete_events() return (-1, -1) @@ -348,7 +351,8 @@ timestamp_end = timestamp_end if timestamp_end is not None else -1 return (timestamp_start, timestamp_end) - @dbus.service.method(constants.DBUS_INTERFACE, in_signature=, out_signature=) + @dbus.service.method(constants.DBUS_INTERFACE, in_signature=, out_signature= + ) def DeleteLog(self): Delete the log file and all its content @@ -430,7 +434,8 @@ # Notifications interface @dbus.service.method(constants.DBUS_INTERFACE, - in_signature=o(xx)a(+constants.SIG_EVENT+), sender_keyword=owner) + in_signature=o(xx)a(+constants.SIG_EVENT+), sender_keyword=owner, + byte_arrays=True) def InstallMonitor(self, monitor_path, time_range, event_templates, owner=None): Register a client side monitor object to receive callbacks when events matching *time_range* and *event_templates* are inserted or ___ 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] [Dev] Upcoming release (0.8.0)
On Fri, May 6, 2011 at 1:01 AM, Federico Mena Quintero feder...@novell.comwrote: On Thu, 2011-05-05 at 22:57 +0200, Siegfried-Angel Gevatter Pujals wrote: Just a quick mail to mention that I'm planning to release Zeitgeist 0.8.0 Saturday night. Releases of libzeitgeist, data-sources, global-privacy (whatever it's definitive name will be) and all should follow soon, at the discretion of whoever takes the role of Master of the Tarball [0]. Thanks for taking the lead on this :) We really need to make packages available for the major distros, and the lack of tarballs (e.g. for zeitgeist-dataproviders) is a big problem. Projects won't take us seriously unless we have regular tarball releases. (Hmm, is zeitgeist-dataproviders renamed to zeitgeist-datasources now?) yes it was renamed. Manish fixed all possible bugs and should be packaging it for release too :) Federico ___ Dev mailing list d...@lists.zeitgeist-project.com http://lists.zeitgeist-project.com/cgi-bin/mailman/listinfo/dev ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
