submissions to bug reports are not integrated

[Kiri]

I am able to file a bug report.
When I post something to the bug report afterwards it is not integrated or does not appear on the report. There is no error message or other sign of error. I do not know what the cause might be.

I do not remember whether it always happens.
Due to this error, I might not be able to provide further information on this or other bug reports.

Browser is firefox.

[Kiri (kiri)]

Test.

[Gavin Panella (allenap)]

Has it happened just once, or more than once? It may just be a transient failure, network perhaps, or something like that. There don't seem to be any general problems with commenting on bugs.

[Kiri (kiri)]

It has happened multiple times in approximately the past 4 to 6 months. Once was when I submitted an attachment, the attachment did not arrive. I did not observe this problem when I first started bug reporting on launchpad. Repeating my submission within the same session after failure generally works.

[Gavin Panella (allenap)]

Thanks for the reply Kiri. When this happens again, please can you note any OOPS numbers that might be reported to you, anything else that appears odd, and describe exactly what you did, and refer to the bug you were trying to comment on.

[Kiri (kiri)]

I tried twice to submit responses to 653171 and once to this report.
Each time, it shows the "Saving" notice, which never ends.
10minutes later it still shows "Saving".

[Kiri (kiri)]

and my submission is not integrated.

I am not sure whether it always showed an unending "Saving" or whether it sometime ended.

[Kiri (kiri)]

Although I see "Saving" the web browser has no TCP connections open, as seen with netstat.

[Gavin Panella (allenap)]

Unfortunately we need more information to diagnose this problem. I'm marking this bug as a duplicate of a bug about displaying more useful information about errors. Hopefully the underlying cause will be apparent when that work is complete.

[Kiri (kiri)]

I don't see how fixing that bug will help with this, since in that bug there is an error message and in this one there is no error message. Whereas in the other error case, it is recognized as an error and there is an error message, in this case there is none. There is no sign that some part of the system recognizes it as an error.

[Gavin Panella (allenap)]

Kiri, in the second comment in bug 521447 Deryck Hodge says:

  My thinking is that this will be a general "better error reporting"
  bug, and once we have the infrastructure in lazr-js, we can open
  bugs about any remaining specific cases after this work is done.

So, I'm going to mark this bug as a duplicate again because there's
nothing we can do here without some work on error reporting. There's
also no way to say it *isn't* a duplicate of bug 521447.

I would prefer to say that this bug depends on the other, but we don't
have bug dependencies (yet) and marking this as a duplicate is, for
now, the best way to hack that relationship into the model.

[Kiri (kiri)]

> I would prefer to say that this bug depends on the other, but we don't
> have bug dependencies (yet) and marking this as a duplicate is, for
> now, the best way to hack that relationship into the model.

Makes sense.