This is fixed at revision#67143.
Thanks for the report.