footgun protection against undefined behaviour when multiple rules have the same priority
Opened this issue · 0 comments
bhearsum commented
Right now, if an update query matches multiple rules with the same priority, it's not possible to guarantee that a certain one is chosen. This is undefined behaviour and can lead to lots of confusion.
We should do something to make this less of a footgun. In the past we've talked about possibly choosing the "most matching" rule (that would be, the one with the most specificity, ie: one that requires build_target+channel is more matching than one that requires just channel).
Another idea could be to just disallow rules with the same priority. Or maybe disallow rules with the same priority when product is the same.
(Imported from https://bugzilla.mozilla.org/show_bug.cgi?id=1283568)