We've been notified about this issue and we'll take a look at it shortly.
It looks like this was the result of either: