Thanks for the head's up about this. If I am interpreting the latest check in notes from the Programming Team, a fix for this issue is being tested now. Look for an upcoming patch.