Gordon, this is the same bug. It's fixed in 0.20 branch *after* 0.20.0 release. The fix *will* be released as 0.20.1
Gordon, this is the same bug. It's fixed in 0.20 branch *after* 0.20.0 release. The fix *will* be released as 0.20.1