We've submitted a fix for this, so it should be in soon. Thanks, everyone!