[Zeitgeist] [Bug 704576] Re: Please update the cheese dataprovider and get it merged upstream
** Changed in: zeitgeist-dataproviders Assignee: Michal Hruby (mhr3) = Seif Lotfy (seif) -- You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Data-Sources. https://bugs.launchpad.net/bugs/704576 Title: Please update the cheese dataprovider and get it merged upstream Status in Zeitgeist Data-Providers: Confirmed Bug description: Some 5 months back Michal created a cheese plugin and submitted it on gnome bugzilla. As per Daniel, it needs to be fixed so that it can merged. The URL is https://bugzilla.gnome.org/show_bug.cgi?id=627311 Assigning it to mhr3 ___ 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 744818] Re: Don't crash on daemon start if a running zeitgeist daemon instance is found
** Branch linked: lp:~zeitgeist/zeitgeist/zeitgeist-0.7.2 -- 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/744818 Title: Don't crash on daemon start if a running zeitgeist daemon instance is found Status in Zeitgeist Framework: Fix Committed Bug description: Instead of exposing the RuntimeError to our users we should simply exit with a status !=0 and log the traceback. ___ 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 738555] Re: zeitgeist-daemon crashed with IOError in _write_to_disk(): [Errno 2] No such file or directory: '/home/royg/.local/share/zeitgeist/datasources.pickle'
** Branch linked: lp:~zeitgeist/zeitgeist/zeitgeist-0.7.2 -- 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/738555 Title: zeitgeist-daemon crashed with IOError in _write_to_disk(): [Errno 2] No such file or directory: '/home/royg/.local/share/zeitgeist/datasources.pickle' Status in Zeitgeist Framework: Fix Committed Status in “zeitgeist” package in Ubuntu: Incomplete Status in “zeitgeist” source package in Natty: Incomplete Bug description: Binary package hint: zeitgeist lsb_release -rd Description: Ubuntu Natty (development branch) Release: 11.04 ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: zeitgeist-core 0.7-1 ProcVersionSignature: Ubuntu 2.6.38-7.36-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 Architecture: amd64 Date: Sun Mar 20 07:40:48 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/zeitgeist-daemon InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20110318) InterpreterPath: /usr/bin/python2.7 ProcCmdline: /usr/bin/python /usr/bin/zeitgeist-daemon ProcEnviron: SHELL=/bin/bash LANGUAGE=en_AU:en LANG=en_AU.UTF-8 PythonArgs: ['/usr/bin/zeitgeist-daemon'] SourcePackage: zeitgeist Title: zeitgeist-daemon crashed with IOError in _write_to_disk(): [Errno 2] No such file or directory: '/home/royg/.local/share/zeitgeist/datasources.pickle' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ___ 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 772041] [NEW] Timestamp isn't considered when choosing events by popularity
Public bug reported: Currently the MostPopular* and LeastPopular* methods are choosing a random (*) event from within all events matching the criteria. Is this desired? I believe it'd make more sense to return that one with the highest timestamp for MostPopular* and the one with the oldest timestamp for LeastPopular*, or something along that lines (there are currently such timestamp ASC/DESC statements in the code, but they aren't working, so if we agree on this property they need to be fixed). (* Actually, it's the last one which was inserted into the database, but that doesn't mean anything.) ** Affects: zeitgeist Importance: High Status: New ** Changed in: zeitgeist Importance: Undecided = High -- 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/772041 Title: Timestamp isn't considered when choosing events by popularity Status in Zeitgeist Framework: New Bug description: Currently the MostPopular* and LeastPopular* methods are choosing a random (*) event from within all events matching the criteria. Is this desired? I believe it'd make more sense to return that one with the highest timestamp for MostPopular* and the one with the oldest timestamp for LeastPopular*, or something along that lines (there are currently such timestamp ASC/DESC statements in the code, but they aren't working, so if we agree on this property they need to be fixed). (* Actually, it's the last one which was inserted into the database, but that doesn't mean anything.) ___ 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 740911] Re: Timed-out testcases should be marked as SKIPPED, or FAILED
Apparently cb_timeout() is running in it's own world. Even if I create a class variable, and change it inside cb_timeout, when I check it outside the timeout afterwards it hasn't changed. Really weird... -- 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/740911 Title: Timed-out testcases should be marked as SKIPPED, or FAILED Status in Zeitgeist Framework: Confirmed Bug description: We do not know if the testcases which time out (I currently have towo of them) really pass, so we should not mark them as such. In newer versions of python we should use SKIP, but I guess FAILED is fine too. Alternativly we should invest some time to find out why they time out and fix them. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
