Hey, thanks for the report. This looks like a processing issue with our image handling server. I'm taking a deeper look.
