I can reproduce the issue and have filed an internal bug to track it. Thanks for reporting the issue!
