Unfortunately, due to a bug in an old cleanup query and a behaviour change in PDO/MariaDB, around 70% of crash reports have been irretrievably deleted. It looks like the distribution was fairly uniformly random, so a fairly representative set should remain. My apologies for any inconvenience this causes.
Spoiler
Code:
[19:54:11] <asherkin> that is a new one - after a major OS upgrade, Throttle decided to delete 40,000 crash reports
[19:54:18] <+r> <Techno> rerm
[19:54:19] <+r> <Techno> wat
[20:01:45] <asherkin> found a stupid bug in a mysql query, really scared that it managed to behave like that though
[20:02:32] <Fyren> rm -rf / WHERE 1=1
[20:10:24] <asherkin> so I was passing in an array of strings bound using PARAM_INT_ARRAY (should have been PARAM_STR_ARRAY), post-upgrade this caused them to force-coerce to ints (so mostly 0), when used in the IN clause, mysql was converting the strings in the table to ints as well (so also mostly 0), which caused almost every row to match rather than the handful intended
[20:12:56] <asherkin> "DELETE FROM crash WHERE id IN (9223372036854775807, 0);" was ran rather than the intended "DELETE FROM crash WHERE id IN ('4e27s3wjixm7', 'ya2vzw75djx6');", and the former matched almost every row due to:
[20:12:57] <asherkin> Truncated incorrect DOUBLE value: '23ww4o2233lf '
[20:13:17] <asherkin> this is fairly high up there in most wtf bug ever
[20:18:00] <asherkin> it seems insane for both a) the data in the table to be the one cast, and b) to cast to the more restricted type
[20:28:26] <+r> <Sikari> Ouch.