Hi Eric, this has now been fixed in rev#74594.