This was a bug indeed. Thanks for reporting, fixed.