Thanks for reporting. I think we have a fix for this; it will get deployed with the next release.