This is follow up for Issue #816. We've just got the same exception even with latest 1.4.3 version. I've reviewed the PR #817 and noticed that the problem was fixed on line 77 but on line 71.