Confirming - we found and fixed the issue. It will go out the door in our next release, which should be Jan 6th.
