This has been resolved internally and will be included in our upcoming patch. Thank you for reporting!