This is fixed now, thanks for reporting.