It was reported here (although I think you posted it about an hour or two earlier).
In any case, there’s a fix for this.