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.
Issue #, if available:
N/A
Description of changes:
In another project we experienced failures using http 1.1 over TLS. This was tracked to
hyper
where we believe we had a slightly different manifestation of this issue hyper 1439 (in our case a closed connection was being used leading to a "Failed to fetch" error).The
hyper
was fixed inv0.13
which is obtained by bumpingreqwest
from0.9
to0.10
.In
reqwest
0.10 the non-async api is relegated to thereqwest::blocking
module. This is breaking for customers oftough
sincepub type HttpTransport = reqwest::Client;
becomespub type HttpTransport = reqwest::blocking::Client;
. However the code changes required to accommodate this are as simple as adding::blocking::
to the path wherever the compiler complains.This change was tested in an update program that uses
tough
and was found to fix the issue.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.