From 5637e04cece2ac4e26e31652c085f720e83a4dc1 Mon Sep 17 00:00:00 2001 From: Klaas van Schelven Date: Thu, 3 Jul 2025 13:23:08 +0200 Subject: [PATCH] Assert no automatic cascades happen in our manual dep-deletion --- bugsink/utils.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/bugsink/utils.py b/bugsink/utils.py index cd0f6e8..7395733 100644 --- a/bugsink/utils.py +++ b/bugsink/utils.py @@ -302,8 +302,9 @@ def delete_deps_with_budget(project_id, referring_model, fk_name, referred_ids, do_pre_delete(project_id, referring_model, [d['pk'] for d in relevant_ids_after_rec]) - my_num_deleted, _ = referring_model.objects.filter(pk__in=[d['pk'] for d in relevant_ids_after_rec]).delete() + my_num_deleted, del_d = referring_model.objects.filter(pk__in=[d['pk'] for d in relevant_ids_after_rec]).delete() num_deleted += my_num_deleted + assert set(del_d.keys()) == {referring_model._meta.label} # assert no-cascading (we do that ourselves) # Note that prune_orphans doesn't respect the budget. Reason: it's not easy to do, b/c the order is reversed (we # would need to predict somehow at the previous step how much budget to leave unused) and we don't care _that much_