-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Result file upload exception #191
Comments
We have identified this on an RPi in the field:
|
I could not reproduce this issue, but it is highly possible that this is caused by urllib3 incompatibility with new pyopenssl library. Reference: urllib3/urllib3#717 The urllib3 version on my machine is 1.9.1, and the newest version is 1.13. @rpanah and @sneft could you confirm the urllib3 version on your machine or RPi and try to update urllib3? |
pip levels are at:
problem persists after upgrade of urllib3 from 1.9.1 to 1.12 1.13 wasn't offered by pip after pip install -U |
The bug reporter of urllib3/urllib3#717 is also using urllib3 1.12. My guess is that they haven't released a new version that contains this fix? |
Yeah. I could set the dependency version to the last good version for now.
I'll test this solution.
|
|
Still happening with: and after installing libcurl4-openssl-dev |
@sneft, you should uninstall PyOpenSSL. Let me know if that fixes your problem. |
Looks like this worked. Thanks! |
I was able to identify the real cause of this issue. The exception is caused by the urllib3 code inside requests package. As you can see, the path in stack trace is "/usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/contrib/pyopenssl.py". And this is why upgrading urllib3 doesn't make a difference. On my machine, This issue is resolved by upgrading requests package from 2.8.1 to 2.9.1. Someone please verify this solution, so that we could add requests and correct version into repo. No need to uninstall pyopenssl. |
This seems to be caused by the newer versions of
PyOpenSSL
. The upload mechanism has to be changed to become compatible with the new library.The text was updated successfully, but these errors were encountered: