Quick update, this is now fixed internally. Once the fix is ready to be put out, we will patch it in. Thank you!