ok, we're aware of that issue, we've got a fix planned which should be implemented pretty soon