Ok, I'll assume then that v1.07 has fixed the issue. Feel free to reopen the ticket if you have a way to reproduce the issue.
Ok, I'll assume then that v1.07 has fixed the issue. Feel free to reopen the ticket if you have a way to reproduce the issue.