This bug is fixed in revision#69315.

Thanks for your report.