Thanks for reporting.

This is fixed in rev#68479