Thanks for the report. This is fixed in rev#92365.