2 ms·
Sounds like an incorrectly scoped WHERE (or maybe even JOIN?) on a SQL query. Plus inadequate (automatic) testing, that should have caught the problem before i
by justinclift 3y ago
Sounds like an incorrectly scoped WHERE (or maybe even JOIN?) on a SQL query.
Plus inadequate (automatic) testing, that should have caught the problem before it was committed to the main development tree.
- selalipop 3y agoSounds more like a typical caching issue than anything
- justinclift 3y agoGood point, yeah that would do it too.
- spondyl 3y agoYeah, it sounds pretty identical to a caching issue that happened to Steam way back on Christmas Day of 2015: https://store.steampowered.com/oldnews/19852 https://store.steampowered.com/oldnews/19852
- lathiat 3y agoYep, plenty of these that have come up over time. Can't think of the names of them at this point but I am sure I recall at least 5+ incidents of exactly this caused by incorrect caching.