>>903
This bug has been fixed with v1.10.2.