Thanks for your bug report. I was able to reproduce this issue. This issue has been fixed for the next version.