This bug is fixed in revision#69172.

Thanks for your report.