Saw a duplciate issue get created in Jira (race condition?) #18
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/critical
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
While triaging this somehow I saw a race condition occur that I think resulted
in two duplicate tickets getting filed:
migtools/crane#83
https://issues.redhat.com/browse/MTRHO-71
https://issues.redhat.com/browse/MTRHO-70
I think what happened here is that I might have added an assignee that caused
a second action to run at the same time as the first, and the labels hadn't
been added yet. I'm not sure how you lock the operation so that this can be
avoided but we'll have to figure out a way to address actions that run in
parallel.
The text was updated successfully, but these errors were encountered: