This is a know issue, will be fixed in the next release. In fact, I just pushed the code that fixes this :)