This issue has now been resolved, thanks for the bug report.