Yes, I just looked that up and realized that the correction was in 1.0.159. I will see if I can duplicate that issue.