duplicate cherry picks issu esp when receiving 'CommandError: 4:Deadline Exceeded' in gitlab.com
Summary
Multiple duplicate cherry picks created on repeated requests within a short period of time. This occurred when the first time I requested I received a 'CommandError: 4:Deadline Exceeded' and later discovered that it had been processed
Steps to reproduce
create a commit on one branch, options, cherry pick, untick create a merge request. While you are waiting for it to complete, optionally get an error message in red 'CommandError: 4:Deadline Exceeded', then make the request multiple times review the graph and you will see the multiple duplicate cherry-picks.
Example Project
I haven't time to do this right now.
What is the current bug behavior?
You get the extra commits in the branch
What is the expected correct behavior?
You receive a message about the cherry pick before another can be committed.
Relevant logs and/or screenshots
I have a screenshot of the duplicates on the onpurpose/onpurpose project - there are two duplicated cherry picks:
Output of checks
This bug happens on GitLab.com