-
Notifications
You must be signed in to change notification settings - Fork 36
Downloading the binaries through a proxy #49
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
base: master
Are you sure you want to change the base?
Conversation
Cargo.toml
Outdated
|
|
||
| [build-dependencies] | ||
| ureq = "1.0" # allows to keep MSRV 1.41.1 | ||
| ureq = "2.1" |
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.
I hope it's ok to use the same version as electrsd. With this old version, the proxying didn't work, or at least not the same way as in electrsd.
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.
sorry for not giving an update on this but I prefer to put this in standby at the moment
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.
2b95f70 to
faa9230
Compare
93df4cd to
6e8ba5e
Compare
09fb8d2 to
5c83cc7
Compare
f57ec64 to
8b0fc8e
Compare
|
After #102 I would be inclined to accept this if you want to fix conflicts |
8b0fc8e to
388a6b3
Compare
|
ok, rebased. |
388a6b3 to
a697cc6
Compare
|
I don't think the CI build error in 1.41.1 has anything to do with my changes. |
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.
I don't think the CI build error in 1.41.1 has anything to do with my changes.
It doesn't which dep broke msrv with their new 4.4.0 version... Don't know what is best to do if pinning the dep or including a Cargo.lock, @Kixunil what do you think?
UPDATE: I'll go with this suggestion instead #104 (comment)
In the meantime I changed the strategy with our CI a bit. Now RCasatta/electrsd#51 would be more important to me,
I'll do my best to tackle that one too
| println!("url:{}", url); | ||
| let mut downloaded_bytes = Vec::new(); | ||
| let resp = ureq::get(&url).call().unwrap(); | ||
| assert_eq!(resp.status(), 200, "url {} didn't return 200", url); |
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.
I don't remember exactly why this assert is here but maybe it helps with reporting? Can we restore it?
a697cc6 to
aae9db7
Compare
| - uses: actions-rs/cargo@v1 | ||
| with: | ||
| command: update | ||
| args: -p which --precise 4.3.0 |
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.
Yeah, this is one of two good ways I know of to resolve the MSRV problem.
…P_PROXY environment variable is set. closes rust-bitcoin#48
aae9db7 to
282212f
Compare
Downloading the binaries through a proxy if either HTTPS_PROXY or HTTP_PROXY environment variable is set.
closes #48