The bug that caused this has been fixed.
When an election hits the primary date there were three scenarios that could happen:
- If there aren't more nominees than spots, and the nomination phase hasn't been extended, it gets extended.
- Otherwise, if there are enough candidates to warrant a primary, it goes to primary.
- Otherwise, it skips straight to the election phase.
There was a bug in the logic for checking that the nomination phase hadn't been extended, which caused it to always return false at the point where we were making this decision, keeping the nominations going indefinitely.
I don't know exactly what happened in this case, but I believe the election got extended a second time, a CM got an email about it, and the CM raced to the site to click cancel.
Two fixes have been implemented:
- The check for if the election has been extended has been fixed.
- If we've already extended the election once and we hit the primary date, we automatically cancel the election.