The issue has been identified and a fix will be deployed in an upcoming release. Thank you for bringing this to our attention.
