The issue has been fixed. The fix will be included into v3.3 and v4.0 beta releases.

Thank you again for the report!