This has now been fixed, thanks for the report.