Activity log for bug #352000

Date Who What changed Old value New value Message
2009-03-30 22:33:00 Jonathan Lange bug added bug
2009-03-30 22:33:00 Jonathan Lange attachment added Screenshot-Bug #118587 in Launchpad Bazaar Integration: “Database ID exposed when users try to push to locked branch” - Mozilla Firefox.png http://launchpadlibrarian.net/24549411/Screenshot-Bug%20%23118587%20in%20Launchpad%20Bazaar%20Integration%3A%20%E2%80%9CDatabase%20ID%20exposed%20when%20users%20try%20to%20push%20to%20locked%20branch%E2%80%9D%20-%20Mozilla%20Firefox.png
2009-03-30 22:33:12 Jonathan Lange security vulnerability yes no
2009-04-01 00:10:41 Christian Reis malone: importance Undecided Critical
2009-04-01 00:10:41 Christian Reis malone: status New Triaged
2009-04-01 00:10:41 Christian Reis malone: milestone 2.2.3
2009-04-01 00:30:29 Diogo Matsubara malone: importance Critical High
2009-04-01 00:33:19 Diogo Matsubara malone: importance High Critical
2009-04-01 12:53:33 Diogo Matsubara attachment added ajax-dupe.png http://launchpadlibrarian.net/24629412/ajax-dupe.png
2009-04-01 12:58:54 Eleanor Berger bug added subscriber Michael Nelson
2009-04-01 13:00:38 Eleanor Berger affects malone lazr-js
2009-04-01 13:00:38 Eleanor Berger lazr-js: importance Critical Medium
2009-04-01 13:00:38 Eleanor Berger malone: milestone 2.2.3
2011-10-06 08:41:03 Robert Collins affects lazr-js launchpad
2011-10-06 08:41:12 Robert Collins launchpad: importance Medium High
2012-01-05 04:01:55 Robert Collins visibility private public
2012-01-05 04:48:30 Robert Collins summary "Mark as duplicate" javascript error is too hard to read Developer Mark as duplicate javascript error is too hard to read
2012-01-05 04:48:48 Robert Collins summary Developer Mark as duplicate javascript error is too hard to read javascript errors are too hard to read
2012-01-05 04:50:27 Robert Collins 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. 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.
2012-01-05 06:00:32 Robert Collins summary javascript errors are too hard to read javascript errors are hard to read, not informative, and often ugly
2012-01-05 06:12:51 Robert Collins removed subscriber Launchpad Security