Thanks for the help. We were able to reproduce the issue. It will be fixed in the next release.