Thanks for the report. This is already fixed as per the commit below. It will be deployed to your instance soon.