This has been fixed in v6.0.7