This will be fixed by upstream PR#469, hopefully included in v3.3.1.

-Topi

Reply via email to