@ Brad
I tracked down the exact issue and implemented a fix. It’ll be part of the forthcoming 0.8 release due out within weeks.
