I still get the error on 5.10.2, so it must have been something recent. @ricardoV94 is always fixing things!