Thanks for reporting this! I'll take a look.
I have created a case internally and am working on completing a fix for the issue. Thanks!
This should be fixed on 6.11 Beta 1.
