issue report

A fix for this should be deployed soon, but you can see more details in this thread: