This is a known issue and fixed internally. Thanks for the report.
This is still in the process being QAed before being patched.