Timeout Page suggests trying again later might work but in general it will not

Bug #892824 reported by Dave Walker
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
High
Unassigned

Bug Description

Timeout Page suggests trying again later might work, it won't - it is a lie

"Timeout error
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.

Trying again in a couple of minutes might work."

Dave Walker (davewalker)
summary: Timeout Page suggests trying again later might work, it won't - it is a
- lie)
+ lie
description: updated
Revision history for this message
Robert Collins (lifeless) wrote :

Only cold-cache situations improve with retries, and they are not the bulk of our performance problems.

summary: - Timeout Page suggests trying again later might work, it won't - it is a
- lie
+ Timeout Page suggests trying again later might work but in general it
+ will not
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
tags: added: confusing-ui trivial ui
Revision history for this message
B Bobo (yout-bobo123) wrote :

It seems to be strongly related to how many packages and projects are listed under a bug. The more there are, the slower launchpad gets, and the more likely a timeout is.
Here, for example, is a bug report that has 24 packages / projects listed, and it always times out when you try to add yourself to the bug report ("this bug affects me too").

https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/885324

To test this, just try the following add-me-too link and watch it fail over and over again:

https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/885324/+affectsmetoo

I tried reloading that link using a script over 150 times, once every 20 seconds - it timed out every single time. So far, nobody has been able to add themselves to the bug report yet. It looks like everybody else is having the same problem.

Come on Launchpad devs! Launchpad has been like this for years. It's an epic failure. What's holding up the fix? It's time to get it moving.

Revision history for this message
B Bobo (yout-bobo123) wrote :

OT: How did I suddenly get added to the "affects me too"? I just checked my logs again, and I can every one of my page load attempts resulted in a timeout error. Did an admin manually add me to "affects me too" this bug report? Thanks anyway.

Revision history for this message
B Bobo (yout-bobo123) wrote :

OT: please ignore previous comment. I'm still not in the "affects me too" list, and it still times out when I try clicking the button to add myself to the list.

B Bobo (yout-bobo123)
tags: added: timeout
Revision history for this message
Curtis Hovey (sinzui) wrote :

There is no text change to make based on the bug report. The page says "Trying again in a couple of minutes might work" and that is true for many timeouts.

Changed in launchpad:
status: Triaged → Won't Fix
Revision history for this message
B Bobo (yout-bobo123) wrote :

@Curtis Hovey

"The page says "Trying again in a couple of minutes might work" and that is true for many timeouts."

That is incorrect. The main author of Launchpad has written above that he agrees that in general trying again in a couple of minutes does not work. There are many other people affected by it. It seems to be a real bug.

So, please would you re-open this bug report. I can't re-open it since you seem to have locked it when you changed its status to "Won't Fix".

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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