This is now fixed, just waiting for the patch to be integrated with the 6.0 branch, thanks for the report.