Thanks for reporting, this looks like a bug. We are looking into fixing this very soon.