This is a known bug; one of our developers is working on a fix for it right now.