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

-Topi

Reply via email to