This correction is fixed, available on next release.