Canonical SSO provider

Provide way to trigger an oops

Bug #720784 reported by David Owen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical SSO provider
Triaged
Low
Unassigned

Bug Description

Provide ways to trigger oopses. One way should be a page to hit in a browser, which is protected by team membership, and another should be through the API (as it interacts with oops differently), also protected.

Related to bug #720607.

Revision history for this message
Ricardo Kirkner (ricardokirkner) wrote :

Ubuntu Pay has something for this; it's called poison. It consists of a middleware + some views that allow for generating errors anywhere in the code at runtime.

This should be extracted into a common application that can be shared by pay, sso and any other project.

Revision history for this message
David Owen (dsowen) wrote : Re: [Bug 720784] Re: Provide way to trigger an oops

On Thu, 2011-02-17 at 17:47 +0000, Ricardo Kirkner wrote:
> Ubuntu Pay has something for this; it's called poison. It consists of a
> middleware + some views that allow for generating errors anywhere in the
> code at runtime.

Yes, Pay's poison is a cool system, but I was thinking (for this bug)
something much more simple: a single view that would do nothing except
raise an exception, every single time. The purpose would be to test the
oops machinery end-to-end.

I think it's also worth considering the injectable errors in the style
of Pay though.

Ricardo Kirkner (ricardokirkner)
Changed in canonical-identity-provider:
status: New → Triaged
importance: Undecided → Low
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.