-
So far, I haven’t been able to reproduce this bug. I think it got fixed last December with the refactor release, but there’s one person still reporting this. Because there’s still a report I won’t close this but I will put it in lower priority for now.
-
We might have found a solution. We are merging this fix for the next release.
-
This has been fixed in v0.2.0