-
-
Notifications
You must be signed in to change notification settings - Fork 324
Comparing changes
Open a pull request
base repository: hyperium/h2
base: v0.4.12
head repository: hyperium/h2
compare: v0.4.13
- 9 commits
- 20 files changed
- 6 contributors
Commits on Aug 25, 2025
-
test: window update stream errors count towards local max (#859)
test: more local reset counts
Configuration menu - View commit details
-
Copy full SHA for b9d5397 - Browse repository at this point
Copy the full SHA b9d5397View commit details
Commits on Nov 28, 2025
-
Configuration menu - View commit details
-
Copy full SHA for c342e3f - Browse repository at this point
Copy the full SHA c342e3fView commit details
Commits on Dec 5, 2025
-
fix: Unparent connection span (#868)
The `Connection` struct contains a `tracing::Span` tracking its lifetime. This can be useful. The problem is that this span has as its parent the span within which the connection is created, meaning that it keeps that span alive (not closed) while it is alive. In practice that means, for example, instrumented functions that create connections and store those connections for reuse will not have their spans closed and exported when they end. This commit sets the `Connection`'s span's parent to `None` and gives it a "follows-from" relation to the span in which it was created instead. This shows the causal relationship between them, without tying the creating span's lifetime to the connection's lifetime.
Configuration menu - View commit details
-
Copy full SHA for 7c9a874 - Browse repository at this point
Copy the full SHA 7c9a874View commit details
Commits on Dec 8, 2025
-
fix: auto-release padding from DATA frames (#869)
We did not used to include padding when returning flow control. This now automatically releases any padded length if a DATA frame with padding is received. Closes #867
Configuration menu - View commit details
-
Copy full SHA for e793b24 - Browse repository at this point
Copy the full SHA e793b24View commit details
Commits on Dec 19, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 0fe6457 - Browse repository at this point
Copy the full SHA 0fe6457View commit details
Commits on Dec 22, 2025
-
feat: implement HTTP/2 informational responses support (#865)
Add support for HTTP/2 informational responses (1xx status codes) including 103 Early Hints. This enables servers to send preliminary headers before the final response, improving client performance through early resource discovery and connection establishment. Changes include: - extend client and server APIs to handle interim informational responses - update stream state management for 1xx responses - add test for interim informational response scenarios This implementation follows RFC 7540 and RFC 8297 specifications for HTTP/2 informational responses handling. Co-authored-by: Apu Islam <apuislam@amazon.com>
Configuration menu - View commit details
-
Copy full SHA for e38678b - Browse repository at this point
Copy the full SHA e38678bView commit details
Commits on Jan 5, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 803d8cd - Browse repository at this point
Copy the full SHA 803d8cdView commit details -
fix: do not assign capacity for pending streams (#860)
`Prioritize::send_data` has a check to prevent assigning capacity to streams that are not yet open. Assigning flow control window to pending streams could starve already open streams. This change adds a similar check to `Prioritize::reserve_capacity`. Test `capacity_not_assigned_to_unopened_streams` in `flow_control.rs` demonstrates the fix. A number of other tests must be changed because they were assuming that pending streams immediately received connection capacity. This may be related to #853. Co-authored-by: Sean McArthur <sean@seanmonstar.com>
Configuration menu - View commit details
-
Copy full SHA for 5f40d38 - Browse repository at this point
Copy the full SHA 5f40d38View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2aeb81f - Browse repository at this point
Copy the full SHA 2aeb81fView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.4.12...v0.4.13