Timeout errors from AJAX actions do not display OOPS numbers
Bug #578319 reported by
Gary Poster
This bug report is a duplicate of:
Bug #352000: javascript errors are hard to read, not informative, and often ugly.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
About 45 minutes ago (about 2:45 UTC on May 10) I had repeated timeout errors when trying to change the status of a bug (bug 534363 FWIW) via AJAX. Another user reported similar problems. I saw no OOPS values for you.
Later, it worked fine.
Perhaps this bug should become "errors when trying to change bug status via AJAX do not display OOPS numbers"? Or maybe the OOPSes will show up in the reports eventually.
Revision history for this message
| Deryck Hodge (deryck) wrote | #1 |
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: error-reporting javascript ui |
| summary: |
- Timeout OOPS when trying to change bug status via AJAX + Timeout errors from AJAX actions do not display OOPS numbers |
Revision history for this message
| Deryck Hodge (deryck) wrote | #2 |
To post a comment you must log in.
I think we should focus on better error display for now, since the timeout seemed transient. If we get more consistent timeouts with AJAX actions, we can open a new bug.