In case you’re wondering why there are suddenly bugs numbered in the 8000s when before they were in the 4000s, it appears that today somebody’s custom code went nuts and submitted about 4000 spurious bug reports, which I’ve now closed.
Looks like it is still hammering the tracker
From: uckelman uckelman@nomic.net
To: messages@vassalengine.org
Sent: Thu, October 4, 2012 3:07:33 PM
Subject: [messages] [Developers] What happened to the bug numbers today
In case you’re wondering why there are suddenly bugs numbered in the
8000s when before they were in the 4000s, it appears that today
somebody’s custom code went nuts and submitted about 4000 spurious bug
reports, which I’ve now closed.
Read this topic online here:
https://forum.vassalengine.org/t/what-happened-to-the-bug-numbers-today/5334/1
I just modified the bug script to reject any requests from 129.93.229.141 (prairiefire.unl.edu). If this is your IP address, and you’re reading this, PLEASE STOP.
Can we physically remove the INVALID bugs from the database? When triaging, I like to check new bugs against the All Bugs display and this is now becoming extremely slow to load.
Thus spake Brent Easton:
Can we physically remove the INVALID bugs from the database? When
triaging, I like to check new bugs against the All Bugs display and this
is now becoming extremely slow to load.
I’ve deleted them. Does everything look ok now?
–
J.
Yes, looks good.