Hello hello, this should be fixed now. It's a server issue, not your client. I've applied a temp fix but until I find the time to commit a change into the repo it might un-fix itself...@ me if you see this again in that time.
