This has been fixed in rev#69049.
Thanks for reporting.