If you added one or more secondary regions to your JudgeApps account on or before Friday, August 26, please visit your profile settings and set your secondary regions again. We apologize for the inconvenience.
On Friday, August 26, 2016 at 9:15 AM EDT, I deployed an update to JudgeApps that had an unexpected side effect: it deleted all information about judges’ secondary regions. Although the erroneous code was swiftly changed, the data loss was irreversible.
As both the lead developer for JudgeApps and author of the faulty update, I take full responsibility for this incident. We have taken swift action to prevent future incidents and ensure your data is safe.
Anyone who added a secondary region to their account on or before Friday, August 26 should visit their profile settings and set their secondary regions again. We apologize for the inconvenience.
Was any other data affected?
No. The only data loss was to judges’ secondary regions. All other information on JudgeApps was unaffected.
What steps are you taking to prevent something like this from happening in the future?
Previously, we backed up the main JudgeApps database on an irregular schedule. Now, the database is backed up on a daily basis. If a similar problem occurred again, we could reverse or significantly mitigate the data loss by restoring the most recent backup.
Additionally, all code that we deploy to JudgeApps is peer-reviewed to catch errors (a process that will continue). However, the code that inadvertently dropped the secondary regions table was automatically generated, and received a lower level of scrutiny than it should have. In the future we will be even more cautious when deploying automatically generated code.