Yesterday morning (Friday 18th januari) I released some broken code calculating distances. It might have affected checkers. So if you have received such feedback in form of bug reports, it was my fault. From what I know, everything is fixed now.
I have been playing around with it. If I understand it correctly, I seem to have missed correcting a variable regarding distance. At least that's how I see it in the Git history.
What I did to start with was this:
* Implemented a new better distance-function in SQL stored procedure. Better math.
* The old one used these arguments: lon1, lat1, lon2, lat2, and km
* The new one used arguments: lat1, lon1, lat2, lon2, and meters.
* When I moved the code to the new function, I totally forgot both the argument order, and the unit. Disaster results.
* I then looked at the commit and which files it had touched, and manually went through those to review the code and correct it.
It seems like I missed the LUA callbacks in the last step, because I can't see that I ever adjusted the distance-parameter there. Also by reviewing the code I can see that it has been using $distance/1000. It should be meters all the way now.
By fixing that, your checker script stopped timing out at least. However, whichever user I have tried gives this error:
[string ""]:9: bad argument #1 to 'pairs' (table expected, got nil)
... and that I don't understand. Is it my fault? I can't see that I have touched anything that should cause this issue.
I will commit this and send to the live servers in a few minutes.
> By fixing that, your checker script stopped timing
> out at least. However, whichever user I have tried
> gives this error:
> [string ""]:9: bad argument #1 to 'pairs' (table
> expected, got nil)
> ... and that I don't understand. Is it my fault? I
> can't see that I have touched anything that should
> cause this issue.
Sorry, my fault - while trying what is causing the timeout I removed some piece of code.
Now everything should be back to original code, however I'm still running into a timeout.
Did you already commit the changes to the productional server?