This issue can be closed. It was fixed in 0.6.4.

Reply via email to