This is fixed in rev#68619.