Marion H.

Commented on Internal Server Error 500 When Deleting Closed Eng...·Posted inHelp

(edited)·

Hi Valentijn S., thanks for your response. I attach the relevant traceback. Thanks for the info on DD_DUPLICATE_CLUSTER_CASCADE_DELETE. Indeed the default of this variable changed from False to True. When I set it to False, it works again as before. I think this should have been mentioned in the changelog. Concerning the version I'm now on 2.57.3 Still I think the behavior I reported could be a bug. Yesterday I also tried it on demo.defectdojo.org and was able to replicate the 500 error.

Commented on Internal Server Error 500 When Deleting Closed Eng...·Posted inHelp

Marion H.

I have some additional info on this question: I went back and v2.56.3 is the last one where this worked as I thought it should work. If you need some logging info on the error I get, let me know. I need to extract some.

Posted in Help·

Marion H.

Internal Server Error 500 When Deleting Closed Engagements Due to Foreign Key Constraint Violation

Hi all, previously I cleaned closed engagements. If there was a finding that was an original of duplicates in this engagement and the duplicates were still present in other engagements, the oldest of these duplicates was set as original of the finding and I was able to delete the closed engagement. Now I always get an internal server error 500, when I try to delete these closed engagements: update or delete on table "dojo_finding" violates foreign key constraint I know there were some changes on the delete logic in recent releases but I could not find an info that what I'm trying to achieve is no longer possible. Did I miss any settings that I need to adjust?

6Comments