signee: (unassigned) => Mikkel Kamstrup Erlandsen (kamstrup)
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/839382
Title:
zeitgeist-daemon crashed with SIGSEGV in
FlintT
To anyone with this problem - you don't have to kill/replace the running
zeitgeist-daemon if you see this bug. Simply open
~/.cache/zeitgeist/daemon.log in your favorite editor, check that you
don't have embarrassing or confidential stuff in there[1] and attach it
to this bug.
[1]: If you do, then
You can generate a redacted zeitgeist log with something like:
sed -e 's/file:.*$/file:XXX/g' ~/.cache/zeitgeist/daemon.log >
~/zeitgeist-redacted.log
Replaces all file: URLs in your log with file:XXX.
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, w
Thanks for the logs everyone.
To anyone else experiencing this problem: You don't have to comment here
to register your problem; simply tick the "affects me too" in the top.
We can all totally appreciate that you are burning CPU and we're working
to resolve it asap.
--
You received this bug noti
If someone is seeing this please try running 'top' in a terminal and
check whether the PID of zeitgeist-daemon keeps changing every so
often... I have a hunch that the daemon may be restarting over and over
again...
--
You received this bug notification because you are a member of Zeitgeist
Exten
Ok, I actually have it myself here now - and I can attest that it's
_not_ because Zeitgeist is restarting...
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/722762
Title:
z
Assignee: (unassigned) => Mikkel Kamstrup Erlandsen (kamstrup)
** Changed in: zeitgeist
Status: Triaged => Invalid
** Changed in: zeitgeist (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Zeitgeist
Extensions, whi
Thanks for the help everyone. This should be fixed in zeitgeist-fts-
extension 0.0.11that I just released. On express route to a mirror near
you ;-)
** Changed in: zeitgeist-extensions
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Zeitge
*** This bug is a duplicate of bug 705944 ***
https://bugs.launchpad.net/bugs/705944
** This bug has been marked a duplicate of bug 705944
FTS index corruption
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Ext
** Changed in: zeitgeist-extensions
Importance: Undecided => High
** Changed in: zeitgeist-extensions
Status: New => Triaged
** Changed in: zeitgeist-extensions
Assignee: (unassigned) => Mikkel Kamstrup Erlandsen (kamstrup)
--
You received this bug notification because
(unassigned) => Mikkel Kamstrup Erlandsen (kamstrup)
** Description changed:
+
+ The Zeitgeist FTS extension should be able to automatically recover from
corrupted indexes by rebuilding the index from the Zeitgeist log.
+
+
+ -- Original report -
+
Hallo,
since a fe
** Changed in: zeitgeist-extensions
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/614282
Title:
fts extension is missing nega
No it does not, and I know because it doesn't use sql at all ;-)
My guess is that it triggers this inside the zg engine by calling into
some of the public api, like get_events() or something.
** Also affects: zeitgeist
Importance: Undecided
Status: New
** Changed in: zeitgeist-extensio
revno: 67
fixes bug(s): https://launchpad.net/bugs/617309
committer: Mikkel Kamstrup Erlandsen
branch nick: MASTER
timestamp: Mon 2011-09-05 11:51:19 +0200
message:
Fix bug "fts can SIGSEGV ZG during reindex". This was caused by searching
while rebuilding the index. The Xapian
** Changed in: zeitgeist-extensions
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/705944
Title:
Can't recover from FTS index corru
If you have at least r69 of the fts extension you can test this by
killing zeitgeist, then running:
$ head /dev/urandom > ~/.local/share/zeitgeist/fts.index/postlist.DB
And restarting Zeitgeist. This should cause a reindex. You can verify
this by looking in ~/.cache/zeitgeist/daemon.log. You sho
If you want to try and help verify that this bug is indeed fixed you
need at least r67 of the fts extension. Then open d-feet and run the
ForceReindex() method on the index - and quickly open Synapse or the
Unity dash and type a search string.
As this is a race it may or may not be elusive. So run
*** This bug is a duplicate of bug 722762 ***
https://bugs.launchpad.net/bugs/722762
** This bug is no longer a duplicate of bug 839739
zeitgeist-daemon crashed with DocNotFoundError in _check_index(): Document 1
not found
** This bug has been marked a duplicate of bug 722762
zeitgeist-
Mikkel Kamstrup Erlandsen has proposed merging
lp:~kamstrup/zeitgeist/network-manager-state-fix into lp:zeitgeist.
Requested reviews:
Zeitgeist Framework Team (zeitgeist)
Related bugs:
Bug #841764 in Zeitgeist Framework: "Storage monitor for networkmanager
broken with NM >= 0.9&
Public bug reported:
The storage device monitoring is broken for NetworkManager >= 0.9 since
the latest version of NM broke API. The result is that the 'net' storage
id will always be marked as unavailable.
** Affects: zeitgeist
Importance: Undecided
Status: New
--
You received th
revno: 1802 [merge]
committer: Mikkel Kamstrup Erlandsen
branch nick: MASTER
timestamp: Mon 2011-09-05 14:21:57 +0200
message:
Merge lp:~kamstrup/zeitgeist/network-manager-state-fix. Fixes it so we
support both <0.9 and >= 0.9 versions of the NetworkManager API
** Changed in: zei
Importance: Undecided => High
** Changed in: zeitgeist-extensions
Status: New => Triaged
** Changed in: zeitgeist-extensions
Assignee: (unassigned) => Mikkel Kamstrup Erlandsen (kamstrup)
--
You received this bug notification because you are a member of Zeitgeist
Extensions,
I agree with Seif - I think this bug is fixed in 0.8.1.1 as described by
Siegfried on bug 809569. This is still consistent with people seeing
this when upgrading from older Zeitgeists to 0.8.1.1 since we restart
the daemon on package upgrades, meaning that we restart the old version
befire reinstat
by indexing long URLs (at least 245 bytes long). We
already had a cap at 2000 characters, but that was apparently not good
enough.
** Affects: zeitgeist-extensions
Importance: High
Assignee: Mikkel Kamstrup Erlandsen (kamstrup)
Status: Triaged
** Changed in: zeitgeist-extensions
Mikkel Kamstrup Erlandsen has proposed merging
lp:~kamstrup/zeitgeist-extensions/fts-cap-term-length into
lp:zeitgeist-extensions.
Requested reviews:
Zeitgeist Extensions (zeitgeist-extensions)
Related bugs:
Bug #843668 in Zeitgeist Extensions: "Blowing Xapian max term length cor
** Changed in: zeitgeist-extensions
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/843668
Title:
Blowing Xapian max term length cor
** Changed in: zeitgeist-extensions
Milestone: None => fts-0.0.12
** Changed in: zeitgeist-extensions
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https:/
Despite a persevering effort by your humble correspondent I've not been
able to reproduce this. I just fixed a handful other bugs in zeitgeist-
extension-fts that *could* be related to this bug. Among others a race
condition and a memory/index corruption issue, which rings fairly well
with this bug
** Changed in: zeitgeist-extensions
Status: Fix Committed => Fix Released
** Changed in: zeitgeist-extensions
Milestone: None => fts-0.0.12
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https:/
** Changed in: zeitgeist-extensions
Status: Fix Committed => Fix Released
** Changed in: zeitgeist-extensions
Milestone: None => fts-0.0.12
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https:/
Ok. The updated crash reports looks sensible. I am still quite in the
dark about this, it could be a binding issue or something - do you
guys get it consistently or only occasionally?
So my guess work so far goes something like this: Consider the buggy
expression from the fts.py Python code:
qu
Richard: Sure - I never personally could reproduce this issue, but one
user seemed to get it very reliably. I can check with him to see if we
can narrow it down.
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extension
With the latest fts release we fixed an index corruption bug that was
the most likely cause of this bug. Marking FixReleased
** Changed in: zeitgeist-extensions
Status: New => Fix Released
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the
I have an idea for a fix. You can help me know if it'll work or not by
running this command in a terminal:
dbus-send --print-reply --session --dest=org.gnome.zeitgeist.Engine
/org/gnome/zeitgeist/index/activity
org.gnome.zeitgeist.Index.ForceReindex
It will rebuild your Zeitgeist index (you will
Wow, that is an interesting stack trace. I assume you have less than
1,462,895,201 items in your index? ;-)
Looking at that monstrous doc id it would seem that this is either
memory corruption in the zg process or that it is a corrupted index,
that xapian somehow doesn't detect.
Can you report wh
Right @Izo, that's also ok. This means that it is rebuilding your index.
If you log out and back in, or reboot - do you then still see the bug?
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.la
Thanks Izo, that means that the fix I had in mind wont work :-/
Need some more time to think this through...
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/851389
Title:
For reference this is the diff. I am not gonna apply it as is, as it'll
require a reindex in order to take effect:
=== modified file 'fts/fts.py'
--- fts/fts.py 2011-09-07 08:42:40 +
+++ fts/fts.py 2011-09-27 08:15:08 +
@@ -607,7 +607,7 @@
# usually web URIs, are indexed
There has been a range of fixes in the zeitgeist-extension-fts package.
Be sure that you are running the latest version and check if you can
reproduce. Running 'apt-cache policy zeitgeist-extension-fts' should
report 0.0.12.
--
You received this bug notification because you are a member of Zeitge
Public bug reported:
The Xapian index for the FTS extension should add version metadata to
more easily and cleanly facilitate re-indexing when needed
** Affects: zeitgeist-extensions
Importance: High
Assignee: Michal Hruby (mhr3)
Status: In Progress
** Branch linked: lp:~mhr3/
** Changed in: zeitgeist-extensions
Assignee: (unassigned) => Michal Hruby (mhr3)
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/860362
Title:
FTS doesn't index paths
The attached branch, lp:~mhr3/zeitgeist-extensions/scheme-detection
Remove , by Michal stands a good chance of fixing this issue:
* It fixes a potential race, where we might end up trying to put data in a
corrupt index
* It removes the code branch where exception happens with some simpler logic
Ok. The Desktop team is pushing this to a PPA https://launchpad.net
/~ubuntu-desktop/+archive/ppa (ppa:ubuntu-desktop/ppa). Anyone willing
to test out the proposed fix will be of great help! Thanks in advance.
--
You received this bug notification because you are a member of Zeitgeist
Extensions,
So it looks like we get thrown off (or already is off?) the bus when
calling AddMatch on the session bus. There were some fixes in Zeitgeist
0.8.2 that may have also fixed this issue. Can anyone with
zeitgeist-0.8.2 (it got uploaded to Oneiric last weekI think)
confirm/deny?
** Also affects: zeit
As Manish points out it would be helpful if people could test against
zeitgeist-0.8.2 which just got uploaded to Oneiric, but also with
zeitgeist-extension-fts-0.0.13 which also just got uploaded. There were
some fixes to the setup of the Xapian index that also may have caught
this one.
** Also af
** Also affects: zeitgeist-extensions
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/757727
Title:
Zeitgeist-daemon memory usag
** Changed in: zeitgeist
Status: New => Confirmed
** 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/832092
Title
** Also affects: zeitgeist
Importance: Undecided
Status: New
** Changed in: zeitgeist
Importance: Undecided => High
** Changed in: zeitgeist (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which i
** Also affects: zeitgeist
Importance: Undecided
Status: New
** Changed in: zeitgeist
Status: New => Confirmed
** Changed in: zeitgeist
Importance: Undecided => High
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscrib
Can people open up ~/.cache/zeitgeist/daemon.log in a text editor and
see if there are any embarrassing, or confidential info in there, and if
not attach it to this bug please? (and if there are you can also just
delete those sections and attach it anyway)
--
You received this bug notification be
Can people open up ~/.cache/zeitgeist/daemon.log in a text editor and
see if there are any embarrassing, or confidential info in there, and if
not attach it to this bug please? (and if there are you can also just
delete those sections and attach it anyway)
--
You received this bug notification be
Thanks for confirming this. We need something to go on before we can
proceed with this issue though. Here's what you can do to help:
First install the needed debugging packages:
sudo apt-get install gdb python-dbg libxapian22-dbg
Then when you see the issue drop to a terminal:
pgrep -f zeit
Thanks Nuno. That log is consistent with the trace attached, so that's
nice to know. I did hope that there would have been some interesting
warnings or other in there, but that was not the case :-/
Can people try to briefly describe their setups? What I want to know is
if we are talking completely
Public bug reported:
The shared-desktop-ontologies that we use has recently released version
0.8. Among a range of other new classes it includes nfo:WebDataObject
which is of particular interest to us as it allows us to properly
describe web pages (since nfo:WebDataObject is not a subclass of
nfo:
Public bug reported:
The problem is that nfo:FileDataObject (which we use as manifestation
for all files) has subclasses nfo:RemoteDataObject and
nfo:EmbeddedFileDataObject which we may not be interested in querying
for (at least, we're not in Unity). In Unity we qualify our queries by
restricting
Thanks ViViD this is most useful! If more people could attach traces
similarly (as described in my comment #48) that would be grand.
(or if you can attach an extra trace, ViVid, that is also good, as the
method I outlined will produce a dump from a random location in the
code)
--
You received th
Thanks teddy this looks just fine :-)
--
You received this bug notification because you are a member of Zeitgeist
Extensions, which is the registrant for Zeitgeist Extensions.
https://bugs.launchpad.net/bugs/722762
Title:
zeitgeist-daemon using ~100% of CPU
Status in Zeitgeist Framework:
In
Review: Approve
review approve
Didn't run the test suite, but the code looks clean
--
https://code.launchpad.net/~zeitgeist/zeitgeist/884193/+merge/84412
Your team Zeitgeist Framework Team is subscribed to branch lp:zeitgeist.
___
Mailing list: http
** Branch linked: lp:~rainct/libzeitgeist/update-ontology-feb2012
** Changed in: libzeitgeist
Assignee: (unassigned) => Siegfried Gevatter (rainct)
** Changed in: libzeitgeist
Importance: Undecided => Medium
** Changed in: libzeitgeist
Status: New => In Progress
--
You received
Thanks for digging through this Doughy; I am not sure why Zeitgeist
searches were slowing down, they are usually very fast. I'll attach a
Zeitgeist task to check if anyone there have any ideas...
** Also affects: zeitgeist
Importance: Undecided
Status: New
--
You received this bug noti
On 2 February 2012 12:49, Siegfried Gevatter wrote:
> This doesn't need any changes in libzeitgeist, does it?
Not that I am aware of. It'll just be callers changing the strings
they pass for event/subject attributes. So no API changes.
--
You received this bug notification because you are a mem
** Changed in: libzeitgeist
Status: In Progress => Fix Committed
--
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/884192
Title:
Update to shared-desktop-ontologies-0.8
I don't have any strong opinion for or against, but I think you need to
state some reasoning behind this? :-)
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is the registrant for Zeitgeist Datahub.
https://bugs.launchpad.net/bugs/927938
Title:
Review: Needs Fixing
Functionally tested in Unity and working well. Unit tests passing. However -
There seems to be a fairly bad leak somewhere. Try repeatedly searching for 'u'
or something like that and you'll see the memory consumption go up fairly fast.
--
https://code.launchpad.net/~zeitge
Review: Needs Fixing
1583+void Indexer::Flush ()
1584+{
1585+ db->flush ();
1586+}
This need to be Commit() and db->commit(). See
http://xapian.org/docs/apidoc/html/classXapian_1_1WritableDatabase.html#cbea2163142de795024880a7123bc693.
You should probably also surround it with a
1550+void Indexer::DropIndex ()
Are we not leaking db and enquire in this method?
--
https://code.launchpad.net/~zeitgeist/zeitgeist/fts++/+merge/92022
Your team Zeitgeist Framework Team is subscribed to branch lp:zeitgeist.
___
Mailing list: https
> > Functionally tested in Unity and working well. Unit tests passing. However -
> >
> > There seems to be a fairly bad leak somewhere. Try repeatedly searching for
> > 'u' or something like that and you'll see the memory consumption go up
> fairly
> > fast.
>
> Nope, sorry can't reproduce that, t
Review: Approve
Looking good to me. I'd like someone else to +1 it before we merge though...
Outstanding work Michal!
--
https://code.launchpad.net/~zeitgeist/zeitgeist/fts++/+merge/92022
Your team Zeitgeist Framework Team is subscribed to branch lp:zeitgeist.
__
** Changed in: activity-log-manager
Status: New => Fix Released
** Changed in: ubuntu
Status: Confirmed => Fix Released
** Changed in: ubuntu
Milestone: ubuntu-11.10 => ubuntu-12.04
--
You received this bug notification because you are a member of Activity
Log Manager, which i
The link to the screenie is broken...
--
https://code.launchpad.net/~cando/activity-log-manager/925638/+merge/94543
Your team Activity Log Manager is requested to review the proposed merge of
lp:~cando/activity-log-manager/925638 into lp:activity-log-manager.
@Raffaele: Yes. It should be most easy to integrate Tracker as a lens on
its own or simply as a scope in the files lens. Honestly, with all the
buzz, I am surprised that no one has done so yet. My guess would be that
it could be done in less than 100 lines of Python
--
You received this bug notif
8 + // Blacklist Ubuntu One events...
9 + const gchar *actor;
10 + actor = zeitgeist_event_get_actor (event);
11 + if (strcmp(actor, "dbus://com.ubuntuone.SyncDaemon.service") == 0)
12 + return;
13 + if (strcmp(actor, "dbus://org.desktopcouch.CouchDB.service") == 0)
Another benefit of a separate function is also that we can unit test the
function directly as well.
--
https://code.launchpad.net/~rainct/zeitgeist/ignore-ubuntuone-actor/+merge/99986
Your team Zeitgeist Framework Team is subscribed to branch lp:zeitgeist.
___
Hi all,
Please don't take this as ranting or any personal attack, but I have a
few issues I think I need to bring up regarding the Zeitgeist Engine
development - at least for making it possible for people in similar
situations as me to participate. This email is motivated by the fact
that I used a
2009/6/24 Siegfried Gevatter :
> [Launchpad's lists are working again.]
>
> 2009/6/24 Mikkel Kamstrup Erlandsen :
>> Maybe zeitgeist.api instead of .util - that way it is more clear that
>> it is indeed public api.
>
> Wouldn't this cause confusion? If it wa
2009/7/16 markus korn :
>
> I just found a few issues and a few things I would like to discuss:
> 1a.) although it is stated here otherwise, mimetype is not an optional
> entry, the engine itself will discard events without a mimetype
> 1b.) is mimetype really required for an event? Seif: as you ar
** Branch linked: lp:~kamstrup/zeitgeist/zeitgeist-querymancer
--
Remove Storm ORM dependencie
https://bugs.launchpad.net/bugs/397978
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
Bu
2009/7/17 Seif Lotfy :
> Hey Here is my take again on the issue
> An event is something that happens
> Something happens needs and application to triger it and a target on which
> the happening takes place (in our case a doc, note or webpage)
>
> So my current proposal is to send around a tuple of
2009/7/20 Seif Lotfy :
>
>
>> 2009/7/20 Mikkel Kamstrup Erlandsen
SNIP
> LOVE IT LOVE IT LOVE IT
> however what happens if i want to log an event where the subject has not
> been registered yet?
My initial idea here was to accept that and create a dummy item for
that uri.
2009/7/20 Siegfried Gevatter :
> I tend to agree with your comment but I'm unsure about one thing:
>
>>> With this mindset it also makes sense to differentiate the lookup
>>> functions, so we have something like:
>>>
>>> FindEvents(...filters...)
>>> FindItems(...filters...)
>
> Maybe I'm just mi
Hi Zeitgeisters!
I wrote a longish blog post spilling my brains with a lot of Zeitgeist
thoughts I've been brewing in my head lately. Maybe it is completely
bonkers - http://www.grillbar.org/wordpress/?p=345, or how do you guys
feel?
Don't get me wrong - I don't want to throw the baby out with th
2009/8/2 Seif Lotfy :
> SNIP ...
> FindEvents however will retrun the EventInfo dict as well as the following
> dict (How we do it will be optimized i have a solution for that)
It needs to be an array of item dicts. An event can have several targets.
--
Cheers,
Mikkel
__
2009/8/2 Siegfried Gevatter :
> SNIP...
> What I think we really need to decide now is how we want to represent
> events and items (when returned by FindEvents et all).
I think you hit the nail on the head here. I think the current Zg API
leaves a blurry line for what Zeitgeist actually is. If we
-querymancer-engine
** Changed in: zeitgeist/0.3
Importance: Undecided => High
** Changed in: zeitgeist/0.3
Milestone: None => 0.2.1
** Changed in: zeitgeist/0.3
Assignee: (unassigned) => Mikkel Kamstrup Erlandsen (kamstrup)
** Changed in: zeitgeist
Importance: Mediu
** Branch unlinked: lp:~kamstrup/zeitgeist/zeitgeist-querymancer
--
Remove Storm ORM dependency
https://bugs.launchpad.net/bugs/397978
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
St
Public bug reported:
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 ev
** Changed in: zeitgeist
Status: New => Fix Committed
** Changed in: zeitgeist/0.3
Status: New => Fix Committed
--
Define content and source types in one central place
https://bugs.launchpad.net/bugs/407369
You received this bug notification because you are a member of
Zeitgeist-En
Note that this bug heavily interlinks with:
https://bugs.launchpad.net/zeitgeist/+bug/411399
--
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 Zeitg
I just merged lp:~kamstrup/zeitgeist/zeitgeist-querymancer-engine. And
is *almost* working. Storm is stil the default backend though. To test
it out set the ZEITGEIST_ENGINE=querymancer environment variable.
--
Remove Storm ORM dependency
https://bugs.launchpad.net/bugs/397978
You received this b
Right, as you described here also I take it:
https://lists.launchpad.net/zeitgeist/msg00081.html
--
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
Hi all,
With Siegfried's latest updates (and some trivial fixes from me) the
Querymancer engine is ready for testing before we go gold in 0.2.1.
We *REALLY* need your help to dust out any hidden regressions!
To test it out start you Zeitgeist daemon with
ZEITGEIST_ENGINE=querymancer in the envir
I was just trying to makte this very list open for the general public
to subscribe. Turns out that this is not possible with the current Zg
project structure.
Launchpad (LP) has a one-to-one mapping of teams<->mailing list. So in
effect all on this mailing list has commit access to lp:zeitgeist.
W
My gut instinct says "Require arrays everywhere" in order to make the
API more uniform and clear - so that the signature of a filter can be
written a{sav} (instead of the weaker a{sv} as now).
--
Inconsistency in FindEvents/CountEvents filter
https://bugs.launchpad.net/bugs/404914
You received th
2009/8/12 Siegfried Gevatter :
> We created http://launchpad.net/~gnome-zeitgeist-users for that.
Hmmm... Ok, but it is not very discoverable then...
Also the list name seems to imply this is about the UI development?
--
Cheers,
Mikkel
___
Mailing li
> Well, stuff like "bookmarked" won't be an array ever.
But wont that info be passed in the annotations in the new API?
--
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
Actually I am talking about both. I stand by what you describe in
comment 8 and I myself in comment 3 and you realize in comment 8 :-).
But the question in comment 6 is about something else.
The bookmarked True/False is also a too weak description. It is not fx.
not compatible with the standard h
Ok, but then I am basically saying that the only possible consumer of
the "bookmark" field is the dedicated Zeitgeist UI. This design concerns
me a little...
--
Inconsistency in FindEvents/CountEvents filter
https://bugs.launchpad.net/bugs/404914
You received this bug notification because you are
2009/8/14 :
> Hey,
>
> I'm attaching a tarball of the current zeitgeist-0.2 branch. Please test it
> and see if there's anything missing before we can release 0.2.1. I'd like to
> get it out tomorrow as on Monday I'm leaving for two weeks.
I get a lot of log messages, that seems to indicate all i
Note that events should be regarded as sub types of items, meaning that
an event is comprised of both the relevant row in the item table and the
corresponding row in the event table. This means that events do in fact
have origins.
I do agree, however, that an origin is a URL, and as such should be
Would it be possible for anyone to throw up a draft of the new design?
(keeping a copy of the old database design spec around...)?
--
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-En
101 - 200 of 490 matches
Mail list logo
