-
Notifications
You must be signed in to change notification settings - Fork 5.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
feat: upgrade Reqwest to 0.12 [WIP] #23542
Conversation
dd27eb2
to
4ba9036
Compare
6d71430
to
adae0c0
Compare
@@ -113,12 +113,12 @@ fs3 = "0.5.0" | |||
futures = "0.3.21" | |||
glob = "0.3.1" | |||
h2 = "0.4.4" | |||
http = "1.0" | |||
http = "1.1" | |||
http-body-util = "0.1" | |||
http_v02 = { package = "http", version = "0.2.9" } | |||
httparse = "1.8.0" | |||
hyper = { version = "=1.1.0", features = ["full"] } |
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.
Quick question: would it be possible to bump hyper version to 1.3? Because reqwest has started to depend on hyper v1 since 0.12, and hyper 1.3 has my patch included which sets the initial number of concurrent send streams to a reasonable default value, upgrading hyper to v1.3 could also resolve #21789 too.
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.
Yes, we definitely can. :)
I lost overview. This was dropped in favor for #24056 yes? |
Yes |
Blocked on TLS and deno_kv issues: