It has been fixed in rev#74479.
Thank you for reporting.