From 39ce37e69c41b0140420d4b12c2df858d2451504 Mon Sep 17 00:00:00 2001 From: Momentry Studio Date: Sat, 25 Jul 2026 13:29:47 +0800 Subject: [PATCH] fix: remove premature updateClusterAfterMerge call in merge loop MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Critical bug fix: - updateClusterAfterMerge() was called after EACH trace merge - This caused source group to be deleted after first trace - Remaining traces had no group to merge into Problem flow: 1. Merge trace #1 from Group B → Group A 2. updateClusterAfterMerge(B, A) deletes Group B 3. Try to merge trace #2 from Group B → Group B is gone! 4. Result: All source groups deleted after first trace Solution: - Remove updateClusterAfterMerge() from loop - Let all traces merge successfully - Reload cluster data at the end (Line 1813) - Core API handles the merge, we just refresh UI Impact: - Merge now works correctly for all traces in a group - No premature deletion of source groups - UI refreshes after all operations complete --- src/views/PeopleView.vue | 1 - 1 file changed, 1 deletion(-) diff --git a/src/views/PeopleView.vue b/src/views/PeopleView.vue index 3c1011b..c06e132 100644 --- a/src/views/PeopleView.vue +++ b/src/views/PeopleView.vue @@ -1796,7 +1796,6 @@ async function executeMerge(targetGroupId: string) { target_id: targetTraceId }) successCount++ - updateClusterAfterMerge(g.identity_uuid, targetGroupId) } catch (e) { console.error('Merge trace failed:', srcTraceId, e) failCount++