thank you for the report, this issue should be fixed in v3.3.5. let me know if you encounter more issues (preferably by making a bug report on github)