@kodablah: thanks for finding that bug. a couple of folks have notified us about that, and we're working to resolve it as we speak. cheers!