This is fixed after revision 66702.
Thanks for the report.