Ah yes thanks for bringing this our attention. This appears to be a bug. We will be releasing a fix shortly!
