forked from hyperium/hyper
-
Notifications
You must be signed in to change notification settings - Fork 0
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
rebase local patches on top of v0.14.27 #4
Closed
Closed
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
…der` (hyperium#3006) fix incomplete changes introduced from hyperium#2828
Previously, `to_bytes` would reserve extra space if after two chunks, there was more remaining. It used to reserve however much space the peer advertized. This changes now only reserves up to ~16kb. This way, a slow message with a big body doesn't reserve so much memory, until the data has actually been received. The existing warning to check for a length before calling the function is still the best approach.
Add `poison` method to `Connected`. This allows callers to mark a connection as poisoned which prevents the pool from reusing it on subsequent requests. `is_open` will consider poisoning prior to returning a connection to the pool.
) Add `capture_connection` functionality. This allows callers to retrieve the `Connected` struct of the connection that was used internally by Hyper. This is in service of hyperium#2605. Although this uses `http::Extensions` under the hood, the API exposed explicitly hides that detail.
This patch backports client/conn/http1 and http2 modules from 1.0 to ease transition. It allows code still using 0.14.x to switch to the per-version Connection types available in 1.0. Closes hyperium#3053 Co-authored-by: KOVACS Tamas <[email protected]>
`client::conn::{SendRequest, Connection, Builder, handshake}` are deprecated as they are removed in 1.0. This adds the `deprecated` feature to Cargo, and only when `hyper/deprecated` is enabled will these warnings be emitted. Co-authored-by: KOVACS Tamas <[email protected]>
…ion (hyperium#3201) This allows users to set the configuration option from hyperium/h2#668.
…ium#3256) If a connection has any error besides reading, a streaming body sometimes wouldn't be notified. This change makes it so that when a connection task is closing because of any error, an existing body channel is also notified. Closes hyperium#3253
Allows adding headers with arbitrary casing so that we can have headers that are all-caps, all upper-case, or whatever else we want. Co-authored-by: James Lucas <[email protected]>
This allows case-sensitive headers to be added by simply adding a HeaderCaseMap-typed extension to the hyper Request object. Co-authored-by: James Lucas <[email protected]>
svix-onelson
force-pushed
the
onelson/rebasin
branch
from
November 16, 2023 21:36
de2e470
to
e12310c
Compare
svix-onelson
changed the title
rebase local patches on top of v0.14.25
rebase local patches on top of v0.14.27
Nov 16, 2023
svix-onelson
force-pushed
the
onelson/rebasin
branch
from
November 16, 2023 21:45
b71cbee
to
19c6acd
Compare
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.
Filtering on the last 4 commits should show just our local changes:
https://github.com/svix/hyper/pull/4/files/d77c2599bc023b258b90a17f5b633c8b7b0cbd4b..19c6acd14767b769303b8ae274cc30e3f9602d61
The MVSR check is failing, but I'm not sure what to do about it. Tests otherwise seem to be in good shape.