it is a known issue. They fixed it and with 3.1.1 the error appeared again. Should be fixed with upcoming 3.1.2
See comments here:
it is a known issue. They fixed it and with 3.1.1 the error appeared again. Should be fixed with upcoming 3.1.2
See comments here: