This is fixed now in rev#69341. 
Thanks for reporting.