javascript errors are hard to read, not informative, and often ugly
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
I love the new "Mark as duplicate" AJAX stuff -- it makes triage much easier. Yesterday though, I got a rather frustrating bug. Here's how to reproduce it:
1. File a bug (let's call it A)
2. File another bug B.
3. Mark A as a duplicate of B
4. File bug C
5. Mark B as a duplicate of C
6. *boom*
The error message contains text that says that one can't mark a bug as being a duplicate if it has duplicates. Whether or not this is a good idea is separate from this bug report, the bug here is that the content & display of the error are unhelpful.
Specifically:
* It's just a big block of red text, with no line breaks.
* It's a Python traceback
I've attached a screenshot. Since the bug and the traceback are both private, I'm marking this bug private.
Note that this takes many forms and occurs in many places. Fixing this bug will require some centralised error handling and deploying that systematically. (E.g. like the 'ajax requests' developer widget.
| Changed in malone: | |
| importance: | Undecided → Critical |
| milestone: | none → 2.2.3 |
| status: | New → Triaged |
| Changed in malone: | |
| importance: | Critical → High |
| importance: | High → Critical |
| Diogo Matsubara (matsubara) wrote | #2 |
| Eleanor Berger (intellectronica) wrote | #3 |
| affects: | malone → lazr-js |
| Changed in lazr-js: | |
| importance: | Critical → Medium |
| Changed in malone: | |
| milestone: | 2.2.3 → none |
| affects: | lazr-js → launchpad |
| Changed in launchpad: | |
| importance: | Medium → High |
| Robert Collins (lifeless) wrote Re: javascript errors are too hard to read | #5 |
| summary: |
- "Mark as duplicate" javascript error is too hard to read + Developer Mark as duplicate javascript error is too hard to read |
| summary: |
- Developer Mark as duplicate javascript error is too hard to read + javascript errors are too hard to read |
| description: | updated |
| summary: |
- javascript errors are too hard to read + javascript errors are hard to read, not informative, and often ugly |
Non launchpad developers don't get the traceback