Thanks, then this is already fixed in the latest code. Feel free to reopen if it's still not fixed in the next release.