It seems this was fixed in commit f1547e1d5, released with 3.0.6.

- Taylan



Reply via email to