Off-by-one error in passed resolutions pages
It seems there's an off-by-one error in the passed resolution pages - the last listed page currently is the 27th, listing resolutions 131 to 135, but there is in fact a 136th resolution. I presume the problem is cuased by the fact that resolutions are internally numbered with zero for the first. Anyhow, it shouldn't be too difficult for an admin to fix.
Gruenberg
27-12-2005, 22:45
This happens every five resolutions, for the record. There was an explanation before, I think, and also a suggestion it wasn't an immediate priority, but I'm not sure. Anyway, all will right itself when the 137th is passed.
This happens every five resolutions, for the record.
Presumably they're using maxResolution/5 rather than (maxResolution+1)/5 to calculate the number of pages.
SalusaSecondus
07-01-2006, 20:18
Presumably they're using maxResolution/5 rather than (maxResolution+1)/5 to calculate the number of pages.
Excellent guess, but the error is actually that we are accidentally passing the ending index as opposed to the length of the array. I've writting the fix and it will go out in our next major deployment cycle. (Ok, so another function or two deeper in the stack, you're right.)