A fix for this has been written and tested. It should be part of the 10.0.3.1 beta which we aim to release in about a week.