Gail, I’m still seeing this issue in the 5.4.5 snapshot, and I’m trying to confirm that it was built. Can you point me to the commit that fixed this issue, or has it not been pushed?

Thanks.