This issue has been fixed on both master and stable branch 4.3. Please upgrade to the latest version.


Reply to this email directly or view it on GitHub.