I managed to figure out the root cause of this and fixed this in a newer version (v0.10 which has just been released), so it'll go away after v0.10.
