Fix error when duplicate users are merged in approvers list
If a user who belongs to an approval group and also is an individual in
the approval rule, MergeService
will fail in the after_merge
, which
will cause MergeWorker
to retry again. Since the merge has been
successfully merged, MergeWorker
will encounter an error since
MergeService
is not idempotent.
This change fixes the issue by using the Array |=
join method to add an
element to the Array, unless it is already present. This fixes the
immediate bug, but we will have to address the idempotency issues later.
Closes #13488 (closed)
Merge request reports
Activity
added 1 commit
- 07730b0e - Fix error when duplicate users are list in approvers list
changed milestone to %12.3
added devopscreate priority2 typebug labels
mentioned in issue #13488 (closed)
added severity2 label
added Pick into auto-deploy label
1 Warning 6e4a4465: This commit’s subject line is acceptable, but please try to reduce it to 50 characters. Reviewer roulette
Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category (e.g. frontend or backend), and by a maintainer in all other categories.
To spread load more evenly across eligible reviewers, Danger has randomly picked a candidate for each review slot. Feel free to override this selection if you think someone else would be better-suited, or the chosen person is unavailable.
Once you've decided who will review this merge request, mention them as you normally would! Danger does not (yet?) automatically notify them for you.
Category Reviewer Maintainer backend Oswaldo Ferreira ( @oswaldo
)Grzegorz Bizon ( @grzesiek
)Generated by
DangerEdited by 🤖 GitLab Bot 🤖mentioned in issue #32185 (closed)
added 1 commit
- 6e4a4465 - Fix error when duplicate users are merged in approvers list
mentioned in commit 404eee31
Thanks for digging into @stanhu
In terms of idempotency, is there anything specific we can open an issue about ? My understanding is that different merge strategies will potentially have different issues /cc @dosuken123