This fixed was picked up by another change for 5.7.0.5 I'll also check 5.6.2.2 and maybe we can close that as well.