It looks like we've broken something on our system. We've logged the error (#473) and will endeavour to fix it ASAP.