Marking bugs as duplicate doesn't work

Bug #1092 reported by Uphaar Agrawalla
12
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Diogo Matsubara

Bug Description

On trying to mark a bug as duplicate in malone, the following error shows up:

"Sorry, a system error occurred

If you were just adding or changing something, Launchpad probably hasn’t recorded those changes."

Sometimes, however, the message below shows up:

"An error occured.

There are 1 input errors.

Constraint ...

On trying to mark a bug as duplicate in malone, the following error shows up:

"Sorry, a system error occurred

If you were just adding or changing something, Launchpad probably hasn’t recorded those changes."

Sometimes, however, the message below shows up:

"An error occured.

There are 1 input errors.

Constraint not satisfied"

There is no indication as to what the "constraint" is.

Tags: lp-bugs
description: updated
Revision history for this message
Björn Tillenius (bjornt) wrote :

Can you tell me which bug you want to mark as a duplicate, and which bug you want to mark it as a duplicate of?

If think the system error occurs when you try to mark a bug as a duplicate and it's already marked as a duplicate of that bug.

The "An error occured." probably happens when you try to mark a bug as a duplicate of another bug that itself already has been marked as a duplicate of another bug. The error message definitely has to be improved here.

Revision history for this message
Uphaar Agrawalla (uphaar) wrote :

Ok, I clearly recall there was no message saying something like "Success in marking duplicate" after having marked some bugs as duplicates. So I tried again, and the System Error occurred, leaving me clueless.

"The "An error occured." probably happens when you try to mark a bug as a duplicate of another bug that itself already has been marked as a duplicate of another bug. The error message definitely has to be improved here."

This situation produces the "Constraint not satisfied" error. Try marking #841 as a dup of #839. (#843 is marked as a dup of #841)

Why will it not let me mark dup in the latter case? As in this case, it is needed (#839, #840, #841 & #843 are all the same)

Also, like you said, the error messages need to be a lot more descriptive and not something like "System error occurred" or "Constraint not satisfied".

Revision history for this message
Christian Reis (kiko) wrote :

Bjorn, have you picked up the error logs and seen what is the exact problem? It could be a dupee.

Revision history for this message
Brad Bollenbach (bradb) wrote :

I interpret "doesn't work" here to mean "the error message doesn't tell me enough to know what I did wrong." I'm going to try to fix this today, if I have time.

Brad Bollenbach (bradb)
Changed in malone:
assignee: nobody → bradb
status: New → Accepted
Revision history for this message
Diogo Matsubara (matsubara) wrote :

Might be interesting to check this out: bug #2458

Christian Reis (kiko)
Changed in malone:
assignee: bradb → diogomatsubara
Christian Reis (kiko)
Changed in malone:
status: Accepted → Fixed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.