Thanks for pointing it out. We have identified the issue and are fixing it now.