Launchpad itself

OOPS creating a new upstream bug task

Bug #354158 reported by Eleanor Berger
12
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Graham Binns
Launchpad itself 2.2.4

Bug Description

Trying to add a new bugtask for a bug with a task targeting the gvfs package is impossible, because the form page oopses. See OOPS-1188E2274

Tags: lp-bugs oops
Revision history for this message
Eleanor Berger (intellectronica) wrote :

This is blocking ~seb128 and may be affecting other bugs too, so we may want to upgrade this to Critical and CP.

Changed in malone:
importance: Undecided → High
milestone: none → 2.2.4
status: New → Triaged
tags: added: oops
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is affecting some other bugs, I've seen several comments about such issues from people using edge in the recent weeks

Revision history for this message
Graham Binns (gmb) wrote : Re: [Bug 354158] Re: OOPS creating a new upstream bug task

We've seen this OOPS before, but never been able to reproduce it. The
problem is that bug 346886 has lots of unicode characters in it, which
are obviously causing breakages when we're creating bugtracker links. We
can get round it by fixing the bugs' descriptions. I don't think it's
critical; I'll leave it at high.

Changed in malone:
assignee: nobody → gmb
Revision history for this message
Graham Binns (gmb) wrote :

Seb, do you know of any specific bug numbers that this is (other than the one in the OOPS) affecting?

Revision history for this message
Graham Binns (gmb) wrote :

I'll tackle this tomorrow and request a CP, FTR. Marking it Critical requires us to follow certain bureaucratic processes that I don't think we need to worry about in this case.

Revision history for this message
Sebastien Bacher (seb128) wrote :

not sure of specific number now, I've been running into several example but I was using the production version rather than edge to workaround those until today, I will note the next one I run into there

Revision history for this message
Diogo Matsubara (matsubara) wrote :

Graham, depending on the size of the fix, how soon it gets ready and reviewed and how risky it is, you might be able to land it for the re-rollout that will happen tomorrow (2009-02-03) (no specific time yet).

Revision history for this message
Graham Binns (gmb) wrote :

On Fri, Apr 03, 2009 at 12:51:04AM -0000, Diogo Matsubara wrote:
> Graham, depending on the size of the fix, how soon it gets ready and
> reviewed and how risky it is, you might be able to land it for the re-
> rollout that will happen tomorrow (2009-02-03) (no specific time yet).

Right. I'll aim for that. The fix won't be huge, I expect.

Graham Binns (gmb)
Changed in malone:
status: Triaged → In Progress
Revision history for this message
Björn Tillenius (bjornt) wrote : Bug fixed by a commit

Fixed in db r7946.

Changed in malone:
status: In Progress → Fix Committed
Björn Tillenius (bjornt)
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

Subscribing...

Other bug subscribers

Remote bug watches

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