TD errors are because of my bad data with non-utf8 characters. The non-utf8 characters are (were) coming from EDDN. A user of ED Market Connector with an extended character set cmdr name (but still utf8 I think) was sending price updates to EDDN, but the EDDN server was not processing the extended character set and rather sent non-utf8 characters. My derp defence was deleting a non-utf8 character OK before processing but unfortunately there were two characters in the name and my derp defence stupidly only handled one. Of course the derp defence is now getting rid of all non-utf8 rather than just one instance.
I reported it to the ED: Market Connector github initially, and then @Marginal worked out what was going on and @Authornet fixed up the issue on EDDN.
Anyhoo - the DNS server is back up now (which was another thing due to some solar panel guys who did the wrong thing while I was away), I've got rid of the non-utf8 characters in the prices files so TD shouldn't spit out any more errors now.
Cheers,
Maddavo
I reported it to the ED: Market Connector github initially, and then @Marginal worked out what was going on and @Authornet fixed up the issue on EDDN.
Anyhoo - the DNS server is back up now (which was another thing due to some solar panel guys who did the wrong thing while I was away), I've got rid of the non-utf8 characters in the prices files so TD shouldn't spit out any more errors now.
Cheers,
Maddavo
Last edited: