need a features 'scope' for page ids

Fixed in stable r11536 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/11536>.

Marking qa-ok because this is in a bit of the code base not actually used by anything live: its fine to deploy based on edge and staging still working. Will get a losa to disable memcache with it on staging today and get more solid confirmation still.

To QA, on staging:
insert into featureflag (scope, priority, flag, value) values ('BugTask:+index', 0, 'memcache', 'disabled');

and then the bugtask index page should not use memcache. Remove the flag and it should use it again.

e.g. hit /bugs/600000 with the row present and missing and confirm memcache rows sppear/disappear

Not sure if this is good or bad, I see:

    Features: {'memcache': None}
    in scopes {'BugTask:+index': None}

in the comment block; so it looks like it finds the scope, but I can't tell if the disabled value propogates properly or not from this view.

Testing with a ++oops++ shows that there are still memcache calls made, so something isn't glued up quite right yet.

https://lp-oops.canonical.com/oops.py/?oopsid=1725S85

https://bugs.edge.launchpad.net/launchpad-foundations/+bug/644751 asking for this to be more obvious.

I would have expected this to show "{'memcache': 'disabled'}" in the features comment.

<lifeless> poolie: that would be lovely
<lifeless> poolie: if you do 'make run' and visit bugs.launchpad.dev/bugs/1
<poolie> ok, let me answer this roadmap mail then i'll see what i can make of it
<lifeless> poolie: then look at the source, you should see the memcache flag evaluated
<lifeless> if you do ++oops++ on that and look at the oops, you can see memcache calls are made.
<lifeless> poolie: setting the rule in the db as I put in the bug, the scope is found, the flag still evaluates to None, and memcache calls are still made.
<lifeless> poolie: its likely shallow, but I've been elbow deep in this bugtask perf patch.

Turns out I was a muppet; thanks for looking into it Martin.