Missing Results Data On One PC But There On Another #783
-
|
Hello all, odd one this. I have two computers that are running the same version of FastF1 (3.6.0) but when I call session.results from one machine I'm missing data, the other returns data as expected. Some screenshots below for reference. Has anyone else experienced this? What could be causing the difference? A difference in versions of another dependancy perhaps? The code is simply:
The "bad machine" doesnt talk to Ergast/Jolpica either (as flagged up by the FastF1 warnings). Thanks, Andrew |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
That is odd indeed. The missing values are retrieved from Jolpica-F1, so that makes sense in the context of that error. Can you please add the following right after your imports (https://docs.fastf1.dev/fastf1.html#configure-logging-verbosity) That will hopefully print an error traceback. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Philipp, ah ok yes that makes sense. Log attached, a quick look suggests an SSL certificate verification failure. The "bad machine" is on a company network, so maybe the connection is being blocked by their firewall? I get a similar error when I do a straight URL request to Jolpica-F1 too. Thanks, Andrew |
Beta Was this translation helpful? Give feedback.
-
|
The company network explains it. This is more of a Python limitation, really. Python ships with its own SSL certificates. Your company is using a firewall that does man-in-the-middle traffic inspection and then reencrypts the https connection with a self signed cert. That cert is installed on the company PC, so it trusts the connection. Python by default does not use system certs, therefore the error. You should install this package so that Python will use system certs globally: https://pypi.org/project/pip-system-certs/ |
Beta Was this translation helpful? Give feedback.
-
|
@andytratter did this fix your problem? |
Beta Was this translation helpful? Give feedback.
-
|
Sorry Philipp - thought I'd replied. Yes all good now, thanks so much. |
Beta Was this translation helpful? Give feedback.
The company network explains it. This is more of a Python limitation, really. Python ships with its own SSL certificates. Your company is using a firewall that does man-in-the-middle traffic inspection and then reencrypts the https connection with a self signed cert. That cert is installed on the company PC, so it trusts the connection. Python by default does not use system certs, therefore the error.
You should install this package so that Python will use system certs globally: https://pypi.org/project/pip-system-certs/