This should be fixed in v0.21.7. If not, it's definitely fixed in v0.21.8 which has just been released to the public :)
