Yes, thanks for reporting!. It's fixed in the version we deployed today.