NotImplementedError OOPS when reporting a bug

Bug #508302 reported by Ihor Kaharlichenko
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Deryck Hodge

Bug Description

Steps to reproduce:
1. Proceed to phpunit project (https://launchpad.net/ubuntu/+source/phpunit/)
2. Click "Report a bug" link
3. Provide summary (in my case it was: "Please backport phpunit 3.4.3-1 from Lucid to Karmic")
4. Click "Next" button
5. Click "No, I need to report a new bug" button
6. Click "Submit Bug Report" button

Expected results:
A new bug report is created.

Actual results:
 Sorry, something just went wrong in Launchpad.

We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.

(Error ID: OOPS-1477N666)

Tags: lp-bugs oops

Related branches

tags: added: oops
Revision history for this message
Deryck Hodge (deryck) wrote :

This is the common NotImplementedError on +filebug. See OOPS-1477C569, for example.

And for a few more examples:

OOPS-1477A479, OOPS-1477C535, OOPS-1477D443

Changed in malone:
status: New → Triaged
importance: Undecided → High
Deryck Hodge (deryck)
summary: - OOPS 1477 when trying to file a phpunit bug
+ NotImplementedError OOPS when reporting a bug
Revision history for this message
Ihor Kaharlichenko (madkinder) wrote :

> This is the common NotImplementedError on +filebug
Strange indeed. If it is so the how did I manage to file this bug report?

Where can I find the list of OOPS'es you've mentioned above? I've tried to Google for them but no luck :(

Revision history for this message
Deryck Hodge (deryck) wrote : Re: [Bug 508302] Re: NotImplementedError OOPS when reporting a bug

On Sun, Jan 17, 2010 at 7:33 AM, Ihor Kaharlichenko <email address hidden> wrote:
>> This is the common NotImplementedError on +filebug
> Strange indeed. If it is so the how did I manage to file this bug report?
>
> Where can I find the list of OOPS'es you've mentioned above? I've tried
> to Google for them but no luck :(
>

You can't see the OOPS reports, sorry. That was a note I was adding
for myself and other full-time Launchpad developers to help debug
what's going on.

Revision history for this message
Ihor Kaharlichenko (madkinder) wrote :

> You can't see the OOPS reports, sorry. That was a note I was adding
> for myself and other full-time Launchpad developers to help debug
> what's going on.
>
I guess I can fetch the sources of Launchpad and take a look on how are
those OOPS labels generated if I'm such a curious one :)

On the other hand right now I'm not able to file a backport request for
phpunit. Can you suggest another way I can do that while this issue is being
fixed?

And Deryck, thank you for taking care of this bug.

Revision history for this message
Ihor Kaharlichenko (madkinder) wrote :

One more OOPS found during bug submission. This time it was OOPS-1489D1344. Actually it was backport request once again, thus the summary followed the same template.

Could Launchpad react somehow on word backport (e.g. to automatically subscribe backport team) and crash during performing some automatic action?

Revision history for this message
Deryck Hodge (deryck) wrote :

The NotImplementedError is due to a validation error (i.e. someone files a bug against a package that doesn't exist or doesn't fill in the description field) and because of the recent inlining of the dupe finder, the view uses the base class which doesn't implement the showFileBugForm method which should display the errors back to the user.

I'll prepare a fix today, which I think should be to have the base class do something sane, which can still be overridden by sub classes.

Changed in malone:
assignee: nobody → Deryck Hodge (deryck)
status: Triaged → In Progress
Revision history for this message
Diogo Matsubara (matsubara) wrote : Bug fixed by a commit
Changed in malone:
status: In Progress → Fix Committed
Deryck Hodge (deryck)
Changed in malone:
milestone: none → 10.02
Deryck Hodge (deryck)
Changed in malone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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