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