Hi everyone,
Aaron has been working on bug 37225 for a while: https://bugzilla.wikimedia.org/show_bug.cgi?id=37225
...but has hit a bit of a brick wall with the bug. I encouraged him to send mail to the list about it, but he's skeptical that more than a very small set of people can be helpful on this, which is part of why I suspect he hasn't sent mail. Please prove him wrong :)
The bug cropped up a few weeks ago, reported May 30. It's hard to say if this was a bug that was caused by a core change deployed around that time, an extension deployed around then, or if it was a latent bug that people just got fed up enough to finally report around that time. At any rate, it's been a tough one to diagnose.
I think one area where a broad search could be helpful is narrowing down when this first started happening, and narrowing down which deployment must have been the issue. Since we're on a biweekly cycle, it shouldn't be a huge amount of code that contributes to this bug. For example, someone with enough git-fu and having read the bug carefully enough might be able to point to a likely culprit revision.
Thanks Rob
p.s. actually, knowing Aaron and having read the last comment on the bug, I suspect the reason he didn't send a mail is that he seems to be close to figuring this out. Still, if someone narrows this down, that'd really kick butt.