This report was incorrect, it can be resolved personally.
Can you describe how you resolved it on your side? I've worked on that issue a few days ago and now I'm wondering if I can revert that change?
I've included the workaround with v3.19 and will mark it as fixed for now.