Launchpad itself

memcached still active even when flags set to disabled

Bug #644751 reported by Martin Pool
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Low
Martin Pool

Bug Description

In https://bugs.edge.launchpad.net/launchpad-foundations/+bug/634342 Robert is unsure whether the flag is having the intended effect. Perhaps we can improve the developer ui or the documentation.

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 644751] [NEW] should be easier to tell which flags are active

I'm sure its not having the intended effect, but I can't tell why.

Revision history for this message
Martin Pool (mbp) wrote :

We can always do with better docs and debuggability but I'm going to retarget this bug to the specific problem in bug 634342 comments 4-6.

summary: - should be easier to tell which flags are active
+ memcached still active even when flags set to disabled
Revision history for this message
Martin Pool (mbp) wrote :

It's user error in https://bugs.edge.launchpad.net/launchpad-foundations/+bug/634342/comments/4

You wanted

  insert into featureflag (scope, priority, flag, value) values ('pageid:BugTask', 1, 'memcache', 'disabled');

Previously the scope selector 'pageid:' was missing.

With that changed, the memcached sections are indeed gone.

Ideally you would have got at least a warning here or something...

Martin Pool (mbp)
Changed in launchpad-foundations:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.