@girish This is fixed in 1.4.2. Thanks!