This was supposed to be fixed by #17, but this is still happening on version 0.4.5. > I am opening this as an issue for visibility, I had already commented on the PR, and it happens as well to @matteenm