Thanks, this is fixed in rev#94575.