maybeConfirmBugtasks times out on bugs with lots of subscribers

Bug #925937 reported by Mario Moder on 2012-02-03
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description


In bug:

I accidently clicked on "No it doesn't affect me". When I try to set it to "Yes it affects me" I get the following error popup after ca. 5 seconds:

The following errors were encountered:

    Timeout error, please try again in a few minutes.

I'm trying it nearly every day since a week, cleaned my browser cache, tried another browser, no way.


Looks to be timing out generating a notification very inefficiently -
SQL time: 4942 ms
Non-sql time: 4160 ms
Total time: 9102 ms
Statement Count: 781

(this is presumably the second affected user)

Mario Moder (oddfellow) on 2012-02-03
summary: - Yes it affects me does not work
+ Does this bug affect you: Timeout error popup

Easy to reproduce, but the error pop up does not provide an OOPS number.

Changed in launchpad:
importance: Undecided → Critical
status: New → Triaged
description: updated
tags: added: timeout
description: updated
Boris Malkov (hikari968) wrote :

I have this issue too.

Steve Kowalik (stevenk) wrote :


The OOPS turns up in the AJAX log.

William Grant (wgrant) wrote :

Ubuntu's automatic bugtask confirmation is triggered by the new affected user, which then times out setting the status of 6 tasks at once.

William Grant (wgrant) on 2012-10-22
tags: added: bugs regression
William Grant (wgrant) wrote :

This is mostly seen when marking a heavily subscribed/duped bug as affecting you, or when marking a bug as a duplicate of a heavily subscribed/duped one. It can be avoided by having no New Ubuntu tasks on such bugs, as the autoconfirm logic is there to change New tasks to Confirmed.

summary: - Does this bug affect you: Timeout error popup
+ maybeConfirmBugtasks times out on bugs with lots of subscribers
William Grant (wgrant) wrote :

OOPS-1b71898b250e4735021c4ccc265c9bd9 for the dupe case.

Torsten Krah (tkrah) wrote :

Same here:

can't be marked as duplicate of: 1573494

Chris Rainey (ckrzen) wrote :

This bug has not received any comments in over 2-years. If it is still present, please describe a recent example and change the 'Status' to 'Confirmed'.

Changed in launchpad:
status: Triaged → Incomplete
Colin Watson (cjwatson) wrote :

@ckrzen, please don't do this sort of thing to bug reports against Launchpad.

Changed in launchpad:
status: Incomplete → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions