> I'm assuming this is all to do with the big changes currently being
> made to the code but it is very strange.
That's probably not the case ... not sure why this suddenly shows up,
I'd expected that this would have been discovered earlier. I've put
it into our bug tracker for now.