The issue has been fixed in upstream. The fix will be in the upcoming 0.7.16 
release.

Reply via email to