OOPS reports do not show active feature flags

[Francis J. Lacoste]

The set of active feature flag should be part of the OOPS record.

The stack trace can usually help in reverse engineering this, but it would be easier if they were listed explicitely.

[Martin Pool (mbp)]

they should now be in the timeline, which goes in to the oops, through my fix for bug 666765, <https://code.launchpad.net/~mbp/launchpad/666765-features-no-reasons/+merge/84050>. if you can't get at them, please undupe and reopen.

[Martin Pool (mbp)]

ok, so they are in the timeline, and in the oops, eg in OOPS-ffd82753d89b5a74066abd99e0d5c1ef, but it looks like they're not rendered in the html version of the oops. so perhaps this bug needs to be redirected to python-oops or something. also, it would be nice if that page gave you an option to download the oops file.

[Robert Collins (lifeless)]

On Tue, Dec 20, 2011 at 1:46 PM, Martin Pool <email address hidden> wrote:
> ok, so they are in the timeline, and in the oops, eg in OOPS-
> ffd82753d89b5a74066abd99e0d5c1ef, but it looks like they're not rendered
> in the html version of the oops.  so perhaps this bug needs to be
> redirected to python-oops or something.  also, it would be nice if that
> page gave you an option to download the oops file.

python-oops-tools is the analysis console.

-Ro

[Robert Collins (lifeless)]

I think the needed change is just to whitelist them in python-oops-tools.