Then I'm closing the report, as it seems to be fixed with 0.3.6.
But feel free to reopen if you experience again this issue
Then I'm closing the report, as it seems to be fixed with 0.3.6.
But feel free to reopen if you experience again this issue