Thanks, I have reported it internally and it is now fixed.