This has been fixed in rev#74391. Thank you for reporting.