Thanks for reporting. We are aware of this issue and will fix it hopefully in a couple of days. You can follow the progress of the work here: