-
Notifications
You must be signed in to change notification settings - Fork 42
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
Update reqwest to 0.12 #1985
Comments
When I upgrade to reqwest 0.12:
This is fallout from seanmonstar/reqwest#2199 - it's unclear why the change was made, but we can probably keep the old behavior without too much difficulty: diff --git a/proxy/src/main.rs b/proxy/src/main.rs
index d1cb6563..b6e04772 100644
--- a/proxy/src/main.rs
+++ b/proxy/src/main.rs
@@ -165,10 +165,12 @@ async fn main() -> ExitCode {
match proxy().await {
Ok(()) => ExitCode::SUCCESS,
Err(err) => {
+ let mut error = err.to_string();
+ if let Some(source) = err.source() {
+ error = format!("{}: {}", error, source);
+ }
// Try to serialize into our error format
- let resp = ErrorResponse {
- error: err.to_string(),
- };
+ let resp = ErrorResponse { error };
match serde_json::to_string(&resp) {
Ok(json) => {
// Print the error to stderr |
There's a small change in how reqwest errors are printed (see <seanmonstar/reqwest#2199>), so handle that in our code and update one test accordingly. Import a number of audits and trust markers, a few audits will still be needed. Fixes #1985.
I'm not assigning this to myself because there's some Rust audits outstanding and those can be grabbed by others if there's interest (and happy to pair on them as well). Currently:
|
Ah, thanks for offering up the chance to pair here, sorry to have missed it. Reviewing the version bump instead (and getting more familiar with cargo vet). |
The current proxy v2 branch (#1718) has reqwest 0.11, we should update to 0.12 before releasing it. I don't want to do it in that branch since it's already so big.
The text was updated successfully, but these errors were encountered: