We are aware of this bug internally and hope to get a fix in as soon as we can. Thanks for the report.