I'm seeing this in a package I'm working on now. Is there a timeframe for the fix to be released? I see it's been solved in the git repository, but presumably testing is currently taking place before a release? Thanks, Andy