Thanks for reporting this. This will be fixed in release 6.0.6.8912 or greater.