tests: bypass the proxy if testing DNS override #2341
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Could those tests just set |
|
Sure, that sounds a lot smarter 😁 |
If an explicit proxy is configured in the environment, then the request will go through it rather than actually resolving the domain. Either we're hitting the target domain on a weird port which will likely fail, or the proxy straight up denies that weird request. We're hitting this issue in the Ubuntu CI. Amazingly enough, the tests actually passed *once* there, although the exact circumstances that allowed this are still a bit of a mystery.
seanmonstar
approved these changes
Jul 3, 2024
kodiakhq bot
pushed a commit
to pdylanross/fatigue
that referenced
this pull request
Aug 20, 2024
Bumps reqwest from 0.12.5 to 0.12.7. Release notes Sourced from reqwest's releases. v0.12.7 What's Changed Revert adding impl Service<http::Request<_>> for Client. Full Changelog: seanmonstar/reqwest@v0.12.6...v0.12.7 v0.12.6 What's Changed Add support for danger_accept_invalid_hostnames for rustls. Add impl Service<http::Request<Body>> for Client and &'_ Client. Add support for !Sync bodies in Body::wrap_stream(). Enable happy eyeballs when hickory-dns is used. Fix Proxy so that HTTP(S)_PROXY values take precendence over ALL_PROXY. Fix blocking::RequestBuilder::header() from unsetting sensitive on passed header values. New Contributors @schopin-pro made their first contribution in seanmonstar/reqwest#2341 @Ten0 made their first contribution in seanmonstar/reqwest#2353 @thalesfragoso made their first contribution in seanmonstar/reqwest#2249 @nipunn1313 made their first contribution in seanmonstar/reqwest#2361 @Threated made their first contribution in seanmonstar/reqwest#2370 @FlowerCode made their first contribution in seanmonstar/reqwest#2380 @zeling made their first contribution in seanmonstar/reqwest#2378 @murongshaozong made their first contribution in seanmonstar/reqwest#2385 @camio made their first contribution in seanmonstar/reqwest#2388 @alekseysidorov made their first contribution in seanmonstar/reqwest#2356 Thanks again @seanmonstar @nyurik Full Changelog: seanmonstar/reqwest@v0.12.5...v0.12.6 Changelog Sourced from reqwest's changelog. v0.12.7 Revert adding impl Service<http::Request<_>> for Client. v0.12.6 Add support for danger_accept_invalid_hostnames for rustls. Add impl Service<http::Request<Body>> for Client and &'_ Client. Add support for !Sync bodies in Body::wrap_stream(). Enable happy eyeballs when hickory-dns is used. Fix Proxy so that HTTP(S)_PROXY values take precendence over ALL_PROXY. Fix blocking::RequestBuilder::header() from unsetting sensitive on passed header values. Commits 88bd9be v0.12.7 68127f0 Revert "feat: Add impl Service\<http::Request<Body>> for Client and `&'_ C... b2a28f5 v0.12.6 522216e feat: Add impl Service\<http::Request<Body>> for Client and &'_ Client (... 646b1f8 chore: update macOS system-configuration dep (#2368) 85dd6da dns: improve error message for hickory-dns and warn in docs (#2389) bfd31be docs: Improve RequestBuilder::multipart's documentation (#2388) 8c7f338 chore: bump dev-dependency libflate (#2382) dddf877 chore: bump h3 dependency a53c944 chore: fix some comments Additional commits viewable in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If an explicit proxy is configured in the environment, then the request will go through it rather than actually resolving the domain. Either we're hitting the target domain on a weird port which will likely fail, or the proxy straight up denies that weird request.
To work around this, we actually modify the environment variables to make sure that our target domain is in the exception list for the proxy.
We're hitting this issue in the Ubuntu CI. Amazingly enough, the tests actually passed once there, although the exact circumstances that allowed this are still a bit of a mystery.