If an update is skipped (eg. the check for the latest file runs before the latest file exists and then the script doesn't run again until the next day) then the number of rows that need to be updated increases dramatically (10+M). We should check to see if this is a problem and guard against it if so although I think having recovery steps prepared regardless seems useful.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Restricted Task | |||||
| Resolved | kostajh | T294511 2021 Security Team wikireplicas audit | |||
| Declined | None | T284948 Raw IPs of logged-out users disclosed in wiki-replicas | |||
| Resolved | Niharika | T324492 Temporary accounts - MVP | |||
| Resolved | kostajh | T340895 [Epic] IP Info accommodations for temporary accounts | |||
| Resolved | STran | T341395 Display Spur data on IPInfo infobox | |||
| Resolved | kostajh | T339284 Deploy ipoid | |||
| Duplicate | STran | T345237 Investigate: Recovering from skipped updates when pulling from the daily feed |