Thread history

That makes no sense, it is well below hitting anything. There was also an issue with priority battles not having any options because everybody had full pairings, which was some errors, as well as malformed requests which were coming from my university connection, I think they had something to do with the SEACOM cable currently being down.

I've added some logging, so next time it happens I can see exactly what the problem is.

OK, fixed. It was having trouble with a mixture between numpy floats and native Python floats when writing them to the database.

Ah, so this was just some other error with the same message? That's a relief. :-) Turned my clients back on.