-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Add proxy pass through test #1014
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the speedy PR!
Can you also take the chance to update the proxies=
argument in test_enable_account
and test_save_account
? They were included as a safety for the proxy handling, but they have the incorrect format.
"""Test proxy pass through.""" | ||
prox = {'urls': { | ||
'http': 'http://user:[email protected]:5678', | ||
'https': 'https://user:[email protected]:5678'}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you replace the host with either an invalid one, or one that resolves quickly: perhaps 127.0.0.1
? This way hopefully we avoid the delay, while still getting the error.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
The issue is really not the url that is being connected to, but rather the requests module does not care if it cannot establish a connection, it keeps trying up until the max number of connection attempts is made. See issue #992 |
Hmm sounds odd - running the tests locally with Anyway, seems part of another issue indeed - the PR itself is looking ready! |
* add proxy test * update proxies
Summary
Test is bad proxy info raises proxyerror in the API. This means we correctly pass the
proxies
dict to the API. Note that this test takes a while because the API does not check if a connection can be established before trying the max number of times.Details and comments