Thank you very much!
The issue was fixed through the following commits:
—Reply to this email directly or view it on GitHub.