This is now fixed on both master and release/0.3.

Thanks for the report!

Reply via email to