I wonder if something went wrong with this change, which was deployed to staging a bit less than a day ago. I think it will probably get rolled back or fixed soon!
I tried to reproduce the issue myself but couldn't. 
Edit: I think @petercooperjr found the root cause here.