launchpad crashes

[jklowden]

My bug report seems to have timed out as follows:

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.

(Error ID: OOPS-1965AO72)

Really? Launchpad couldn't wait for me to type in the information, and now both reports are gone?
Does that strike you as bogus?

What does "recorded what happened" mean? Did you get it or didn't you?

For the record, there are two bugs: one about the ld.so man page, regarding search order, and one about apport-cli, about reporting documentation bugs. But I have to tell you, I barely *care* anymore. I'm trying to *help*, and the so-called system isn't.

[Robert Collins (lifeless)]

We're sorry you've run into this problem. The search engine used by launchpad is running into performance issues and we are working on it (in the short term we're repacking indices, in the longer term we're looking at ways to optimise the queries/switch to a different search engine).

If you hit F5 and refresh the page when this happens it may well succeed (because the data to serve your request will be in hot cache).

This bug is a duplicate of the one we have about the situation in general and I've marked it as a duplicate as such.

[jklowden (jklowden)]

On Thu, 19 May 2011 04:19:49 -0000
Robert Collins <email address hidden> wrote:

> We're sorry you've run into this problem. The search engine used by
> launchpad is running into performance issues and we are working on it
> (in the short term we're repacking indices, in the longer term we're
> looking at ways to optimise the queries/switch to a different search
> engine).

I appreciate the explanation, Robert, and I don't doubt you're working
on it. As you consider a new framework, could I offer two things that
would make the experience of the would-be bug-reporter easier?

1. Don't lose user input. When I say send, capture the data, *then*
deal with whatever. Honestly, there's no reason -- really, no reason
-- for a webserver to have trouble inserting 150 words into a
database. Ask anyone who accepts credit card orders.

2. Accounts. Feh. For every project, I need an account, and a
password, which I may or may not ever use again, and which when I do
use it may or may not still be valid. Then I have to log in. All to
authenticate *nothing* because, after all, you don't need to know who I
am.

The NetBSD project uses send-pr. At the command line, you type
"send-pr". It brings up a problem-report template, prepopulated with
the details of the system it's running on (which you can can overwrite
if desired). When you save the file and close the editor, the report
is mailed. Job done. Convenient, fast, efficient.

Hope this helps. Thanks for listening.

--jkl