Hey, thanks for pointing this out. We are aware of this and the fix is done, it will be released with the next deploy.