We have a fix incoming for this.