Closed Bug 933944 Opened 11 years ago Closed 10 years ago

rules.html has race condition

Categories

(Release Engineering Graveyard :: Applications: Balrog (frontend), defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: bhearsum)

References

Details

Attachments

(1 file)

Rail discovered this today when re-enabling Aurora updates. If you click "update" on one rule, and then "update" on another rule before the first update finishes, you will end up updating the second rule. This is because there's only one form for all of the existing rules, and clicking on "Update" sets the "rule_id" value of the form, which is read in the Javascript that does the update.

We may need to use a separate form for each rule, or perhaps just pass rule_id to submitRuleForm (rather than passing the ruleForm itself).
Blocks: 596831
I wasn't able to reproduce this locally, but I'm pretty sure this should fix the problem...
Assignee: nobody → bhearsum
Status: NEW → ASSIGNED
Attachment #8364426 - Flags: review?(rail)
Attachment #8364426 - Flags: review?(rail) → review+
Attachment #8364426 - Flags: checked-in+
Depends on: 964396
This patch is in production, and I wasn't able to repro the problem when I was testing against aus4-admin-dev. I'm pretty sure this is fixed...
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Release Engineering → Release Engineering Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: