In-Development TradeDangerous: power-user trade optimizer
- Thread starter kfsone
- Start date
Did something get changed?
TD hasn't been able to process updates for a couple days - so this morning, I removed everything. Even Python. And re-installed. Still cannot process a Maddavo update:
But what's got me totally confused is that I also attempted to re-install an older version of TD. Even that didn't help. Any suggestions?
Thanks
- - - - - Additional Content Posted / Auto Merge - - - - -
Oh yea - and I'm running Python 3.4.2. I was running 3.4.3 for some reason, but I backed it down to the "approved" version.
TD hasn't been able to process updates for a couple days - so this morning, I removed everything. Even Python. And re-installed. Still cannot process a Maddavo update:
But what's got me totally confused is that I also attempted to re-install an older version of TD. Even that didn't help. Any suggestions?
Thanks
- - - - - Additional Content Posted / Auto Merge - - - - -
Oh yea - and I'm running Python 3.4.2. I was running 3.4.3 for some reason, but I backed it down to the "approved" version.
It appears Maddavo has some non-ascii characters in the prices file now. You can see it in the comment for that explosives line.
I'm guessing this has something to do with this update from EDDN where they started accepting non-ascii characters in commander names.
I'm guessing this has something to do with this update from EDDN where they started accepting non-ascii characters in commander names.
Market Connector [Windows]_1.8.7.0Not sure the easiest way on Windows at the moment, but if you have Perl installed, this should work:
perl -pi.bak -e 's,\s+#.*$,,' import.prices
It'll keep a backup in import.prices.bak.
Note: The above was tested on MacOSX / Linux and works, I'm trying to figure out how to hack the plugin Python code now to fix it on actual import.... no luck so far.
perl -pi.bak -e 's,\s+#.*$,,' import.prices
It'll keep a backup in import.prices.bak.
Note: The above was tested on MacOSX / Linux and works, I'm trying to figure out how to hack the plugin Python code now to fix it on actual import.... no luck so far.
Last edited:
Ok, I've found a way to "patch" this to work, although I don't know if this is the "correct" way to fix it, it does work for me. You need to edit 3 lines in 2 files:
1. Edit the "cache.py" file and change this line:
Line 800: with pricesFh or pricesPath.open('rU', encoding='utf-8') as pricesFh:
to this:
Line 800: with pricesFh or pricesPath.open('rU', encoding='utf-8', errors='replace') as pricesFh:
2. Edit the "plugins/maddavo_plug.py" file and change this line:
Line 608: line = line.decode(encoding="utf-8")
to this:
Line 608: line = line.decode(encoding="utf-8", errors="replace")
and change this line:
Line 611: line = line.decode(encoding="latin1")
to this:
Line 611: line = line.decode(encoding="latin1", errors="replace")
Then it should work now, at least it does for me now. Hopefully, @kfsone or @maddavo can fix this properly soon, but for now this seems to do the trick.
Hope it helps someone.
1. Edit the "cache.py" file and change this line:
Line 800: with pricesFh or pricesPath.open('rU', encoding='utf-8') as pricesFh:
to this:
Line 800: with pricesFh or pricesPath.open('rU', encoding='utf-8', errors='replace') as pricesFh:
2. Edit the "plugins/maddavo_plug.py" file and change this line:
Line 608: line = line.decode(encoding="utf-8")
to this:
Line 608: line = line.decode(encoding="utf-8", errors="replace")
and change this line:
Line 611: line = line.decode(encoding="latin1")
to this:
Line 611: line = line.decode(encoding="latin1", errors="replace")
Then it should work now, at least it does for me now. Hopefully, @kfsone or @maddavo can fix this properly soon, but for now this seems to do the trick.
Hope it helps someone.
Last edited:
sceaga - that worked. Still throws errors (mostly unrecognized items), but it let me do an import which gets me back trading. Hopefully others experiencing the issue will have similar results. MANY plus rep points!!
And, yeah, let's hope they get it fixed soon. I suspect, however, that they'll need to do some fairly significant changes for Horizons as well. Your excellent patch buys us all time.
Fly safe!
And, yeah, let's hope they get it fixed soon. I suspect, however, that they'll need to do some fairly significant changes for Horizons as well. Your excellent patch buys us all time.
Fly safe!
I've had a look around and:
- the domain registration still appears to be valid
- the domain registration points to two DNS servers, neither of which seem to be responding in any way;
- the two servers IPs are both from an Australian ISP, but not their official nameservers.
Basically it is possible that the davek.com.au server is still up, but at present nothing knows how to find it.
I think the most likely cause is that the two DNS servers are both down for some reason, and so the rest of the internet has (as it's supposed to) forgotten about the DNS records hosted there over the last day (likely = the cache lifetime of the records.)
Can anyone contact davek other than by email?
- the domain registration still appears to be valid
- the domain registration points to two DNS servers, neither of which seem to be responding in any way;
- the two servers IPs are both from an Australian ISP, but not their official nameservers.
Basically it is possible that the davek.com.au server is still up, but at present nothing knows how to find it.
I think the most likely cause is that the two DNS servers are both down for some reason, and so the rest of the internet has (as it's supposed to) forgotten about the DNS records hosted there over the last day (likely = the cache lifetime of the records.)
Can anyone contact davek other than by email?
I sent a message to his BitBucket account saying we are worried about our Trade Data.
It's the only alternate way of contacting him I know of.
Hi, sorry, I'm away ATM but I'll try to see what I can do from here. I'll be back on Thursday.
I did notice also a few nonutf8 characters get sent via eddn last Fri and Sat and maybe some of the code I wrote to handle that is barfing. Had to go only a few hrs after I wrote it so didn't have time to check it much.
I did notice also a few nonutf8 characters get sent via eddn last Fri and Sat and maybe some of the code I wrote to handle that is barfing. Had to go only a few hrs after I wrote it so didn't have time to check it much.
Darn that real life, getting in the way!
Any connectivity with kfsone as well? LOT's of error codes coming up in Trade Dangerous as well - probably from the same character issues, per the above discussion. Tonight the update just crashed and burned, this weekend sceaga was able to come up with a work-around. Even a "I'm working on it, and it'll be an update associated with Horizons" would be welcome.
And - DEFINITELY not whining! You folks are champs for what you do!
Any connectivity with kfsone as well? LOT's of error codes coming up in Trade Dangerous as well - probably from the same character issues, per the above discussion. Tonight the update just crashed and burned, this weekend sceaga was able to come up with a work-around. Even a "I'm working on it, and it'll be an update associated with Horizons" would be welcome.
And - DEFINITELY not whining! You folks are champs for what you do!