Thanks, this is fixed in rev#91262.