Is it possible that I could find instructions anywhere to have a go? It sounded a bit complicated to meI don't think the certificate problem has anything to do with the windows version, so yeah, probably.
Is it possible that I could find instructions anywhere to have a go? It sounded a bit complicated to meI don't think the certificate problem has anything to do with the windows version, so yeah, probably.
Command: nav --ly-per=32.0 Tabit/Haber City Ceos/Babbage Gateway --pad=M --planetary=N -vvv
Traceback (most recent call last):
File "/usr/local/bin/trade", line 8, in <module>
sys.exit(main())
File "/usr/local/lib/python3.7/site-packages/tradedangerous/trade.py", line 40, in main
cli.main(sys.argv)
File "/usr/local/lib/python3.7/site-packages/tradedangerous/cli.py", line 70, in main
trade(argv)
File "/usr/local/lib/python3.7/site-packages/tradedangerous/cli.py", line 125, in trade
results = cmdenv.run(tdb)
File "/usr/local/lib/python3.7/site-packages/tradedangerous/commands/commandenv.py", line 83, in run
return self._cmd.run(results, self, tdb)
File "/usr/local/lib/python3.7/site-packages/tradedangerous/commands/nav_cmd.py", line 94, in run
stationInterval=stationInterval,
TypeError: 'NoneType' object is not iterable
Just had an error with TD:
Code:Command: nav --ly-per=32.0 Tabit/Haber City Ceos/Babbage Gateway --pad=M --planetary=N -vvv Traceback (most recent call last): File "/usr/local/bin/trade", line 8, in <module> sys.exit(main()) File "/usr/local/lib/python3.7/site-packages/tradedangerous/trade.py", line 40, in main cli.main(sys.argv) File "/usr/local/lib/python3.7/site-packages/tradedangerous/cli.py", line 70, in main trade(argv) File "/usr/local/lib/python3.7/site-packages/tradedangerous/cli.py", line 125, in trade results = cmdenv.run(tdb) File "/usr/local/lib/python3.7/site-packages/tradedangerous/commands/commandenv.py", line 83, in run return self._cmd.run(results, self, tdb) File "/usr/local/lib/python3.7/site-packages/tradedangerous/commands/nav_cmd.py", line 94, in run stationInterval=stationInterval, TypeError: 'NoneType' object is not iterable
MacOS 10.13.6, python 3.7, latest TD. Is it me?
...\Trade-Dangerous\test>..\trade.py nav --ly-per=32.0 "Tabit/Haber City" "Ceos/Babbage Gateway" --pad=M --planetary=N -vvv
H:\eyeonus\eclipse\workspace\Trade-Dangerous\trade.py: No route found between Tabit and Ceos with a max 32.0ly/jump limit.
Yes. "--fleet-carrier", "--fc". Options are any of [YN?] just like with --planetary.Does TD have an ignore carrier flag? If not, please can we have one![]()
Many thanks.It's not just you. I've fixed it, pushing the update now. TD v10.13.7 is now available.
Note: your command as shown above will still give an error with the fix:
Code:...\Trade-Dangerous\test>..\trade.py nav --ly-per=32.0 "Tabit/Haber City" "Ceos/Babbage Gateway" --pad=M --planetary=N -vvv H:\eyeonus\eclipse\workspace\Trade-Dangerous\trade.py: No route found between Tabit and Ceos with a max 32.0ly/jump limit.
Yes. "--fleet-carrier", "--fc". Options are any of [YN?] just like with --planetary.
Just tried the fleet carrier flag and I'm seeing something strange.It's not just you. I've fixed it, pushing the update now. TD v10.13.7 is now available.
Note: your command as shown above will still give an error with the fix:
Code:...\Trade-Dangerous\test>..\trade.py nav --ly-per=32.0 "Tabit/Haber City" "Ceos/Babbage Gateway" --pad=M --planetary=N -vvv H:\eyeonus\eclipse\workspace\Trade-Dangerous\trade.py: No route found between Tabit and Ceos with a max 32.0ly/jump limit.
Yes. "--fleet-carrier", "--fc". Options are any of [YN?] just like with --planetary.
Oh, that's easy enough to explain.Just tried the fleet carrier flag and I'm seeing something strange.
With the flag missing entirely I get a trade to a carrier, with the flag set to 'N' I also get a trade, albeit a different one.
However, if I set the flag to either 'Y' or '?' I get a message stating that there are no routes in-range of any end station at the end of hop 0.
The full command is:
trade run --age=3 --avoid=slaves,narcotics --jumps=1 --lsp=12.5 --margin=0.0 --ls-max=500 --planetary=N --fleet-carrier=N --supply=100 --loop --insurance=4178077 -vvv --progress --summary --cr=14633779956 --cap=752 --ly=18.68 --empty=32.59 --pad=L
I had to type that manually, so I hope I got it all correct.
Great. Thanks.Oh, that's easy enough to explain.
'--fc Y' means only include stations which are fleet carriers: if the station is not a fleet carrier, it is excluded from the search
'--fc ?' means only include stations for which it is unknown whether or not they are fleet carriers: if the fleet carrier status is known, the station is excluded from the search.
'--fc YN' means include stations which are fleet carriers, and stations which aren't, but don't include any where it isn't known.
'--fc N?' means include stations that aren't, or that aren't known, but don't include any that are, fleet carriers.
'--fc YN?' is the same thing as not using the switch at all: all stations are included regardless of fleet carrier status.
The --planetary and --odyssey switches also work like the above, but with stations of those respective types rather than with fleet carriers.
I have found a way to avoid the situation. If I turn on the PC and then leave it alone for an hour or so, then TD works as expected. I'll try reducing the time until the problem resurfaces and then use that as the time the PC needs to sit before using TD.No, but you might be able to get help if you try asking around the Python and/or Win11 communities, as this seems like a general Python/Win11 thing, and not specific to TD.
I wish this would work for me -- I'm missing using TD -- I still get the certificate messages when I try to update.I have found a way to avoid the situation. If I turn on the PC and then leave it alone for an hour or so, then TD works as expected. I'll try reducing the time until the problem resurfaces and then use that as the time the PC needs to sit before using TD.
My guess is that although Windows 11 appears to start up very quickly, behind the scenes, so to speak, it takes a lot longer to get properly started and trying to use TD during this period has problems.
We'll see.
Have you tried the possible solutions found in these two posts?I wish this would work for me -- I'm missing using TD -- I still get the certificate messages when I try to update.
Hi Mark, Thanks very much for your help it's greatly appreciated. I might be doing a windows reinstall soon, as I'm upgrading my computer. It has been suggested that the current installation might be the source of the problem. I will keep this thread updated in case it's of use to anyone else. Thanks againHave you tried the possible solutions found in these two posts?
![]()
Windows: Python SSL certificate verify failed
I've installed Anaconda and had SSL problems when trying to do API calls via Jupyter Notebooks: import requests import certifi r = requests.get('https://github.com/') print(r) This first produced...stackoverflow.com
![]()
Windows: Python SSL certificate verify failed
I've installed Anaconda and had SSL problems when trying to do API calls via Jupyter Notebooks: import requests import certifi r = requests.get('https://github.com/') print(r) This first produced...stackoverflow.com
The first one instructs python to use the Windows certificate store and the second, more complicated method tries to stop the error by Importing 3 certificates into your local Trusted Root Certification Authorities list.
These are mutually exclusive so don't try doing both at the same time.
Personally, I'd try the first one and if that fails, use the "pip uninstall python-certifi-win32" to revert the change and then try the second method.
Has the server fallen over again? My TD stopped updating earlier this afternoon.Another quick update:
You may have noticed TD fallen over again. After we finished our testing for the problem, I did a full reinstall to clean up all the test code and get a clean install of TD on the server. Sadly, it looks like the fix had not propagated to the local github mirror and my server downloaded the old broken version.
I've once again updated the server and manually checked we have the correct code, which we do, so إِنْ شَاءَ ٱللَّٰهُ this won't be a problem again.
Strangely, the server is showing 11 hours uptime, so I can only guess the host server got a reboot. I have restarted the TD service.Has the server fallen over again? My TD stopped updating earlier this afternoon.
Thanks, that did the trick.Strangely, the server is showing 11 hours uptime, so I can only guess the host server got a reboot. I have restarted the TD service.