This issue is now fixed, thanks for the report.