Error displayed when I subscribe someone else

[Micah Gersten]

This error appears when I try to subscribe someone else to a bug:
The following errors were encountered:

    0 () Couldn't get subscriber details from the server, so they have not been subscribed.

If I try a second time, it usually works.

[Deryck Hodge (deryck)]

I'm guessing a timeout, but we really need the error overlay to provide more info to know for sure.

[Deryck Hodge (deryck)]

Which is why I didn't mark this critical yet. :-)

[Bryce Harrington (bryce)]

I've run into this as well. It seems to be pretty easy to reproduce.

1. On this bug, click 'Subscribe someone else'
2. Type in some random user
3. Click on their name
4. Click once more on 'Select'
5. The error Dustin mentioned gets shown. There is no Oops number given.
6. A moment later, with no activity taken, the error dialog disappears and the bug reloads
7. The subscribee is not subscribed
8. Repeat again from #1; this time it works at step #4.

This bug does need to be included with the critical bugs; even without an Oops # it is a regression.

[Bryce Harrington (bryce)]

s/Dustin/Micah/. Sorry micah!

[Robert Collins (lifeless)]

The developer console should let you see the headers for the request,
and from that you can get the OOPS id.

[William Grant (wgrant)]

Seems to be a recent regression, given the duplicate.

[Iain Lane (laney)]

I see this all the time too, and just so this comment has some content: just got it on #832281 if that helps you in locating the OOPS. The overlay disappears too fast to do anything useful with it.

[Benji York (benji)]

I can't reproduce this bug in production or staging. I'm trying to artificially recreate it in dev so I can at least make it a little easier to debug.

[Benji York (benji)]

The "0 ()" at the beginning of the error message are a clue. They are
the result code and text from the XHR request to fetch the user details
about the chosen new subscriber. The fact that the result code is 0
suggests that no response whatsoever was received from the server (not
even a timeout message). I was able to produce the same symptom by
taking down Launchpad as well as Apache on my dev setup just before
subscribing the new user.

[Bryce Harrington (bryce)]

Fwiw, this does not appear to be happening anymore (at least, I've not been able to reproduce it as I described earlier.)

[Jeremy Bícha (jbicha)]

I agree with Bryce, I'm not able to re-duplicate this.