• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In
Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.
New Repo Setting:
INCLUDE COVERAGE % WITH WARNINGS ABOUT DRIFTED BUILDS?

Enabling this setting will include a (potentially inaccurate) coverage % with warning messages in status updates for drifted builds.

Adjust setting

elixir-mint / mint / 963c1d2d24ec052d6470042a26432e5c879509b7-PR-550
90%
main: 90%

Build:
Build:
LAST BUILD BRANCH: http2-manual-stream-window
DEFAULT BRANCH: main
Ran 17 Nov 2026 02:30PM UTC
Jobs 2
Files 22
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

17 Nov 2026 02:28PM UTC coverage: 90.645% (+0.02%) from 90.623%
963c1d2d24ec052d6470042a26432e5c879509b7-PR-550

Pull #550

github

ericmj
Add manual refill of HTTP/2 stream receive windows

Mint refills a stream's receive window as soon as it parses a DATA
frame, so a process that owns the connection and hands body chunks to
other processes can't slow the server down for one request. Finch's
HTTP/2 pool does this: it calls stream/2 and sends {:data, ref, data}
to the caller, so a caller that handles chunks slower than the server
sends them gets an unbounded mailbox (sneako/finch#282). Not calling
stream/2 pauses every request on the connection.

With the new stream_window_refill: :manual connect option, Mint holds
back the data bytes of each DATA frame from the stream refill until the
caller releases them with Mint.HTTP2.refill_window/3. Padding is still
refilled right away since the caller never sees it, and the connection
window keeps refilling on receipt, so a stalled request doesn't block
the others. Released bytes are batched with the existing
:receive_window_update_threshold logic. Releasing data for a completed
or unknown request is a no-op, and releasing more than was received
returns a {:refill_exceeds_received, unreleased, size} error.

set_window_size/3 set the remaining window to the new peak instead of
adding the increment it sent, so growing a window mid-response made Mint
count the bytes received since the last refill as credit the server
still had. When that was more than :receive_window_update_threshold
(160 KB by default) the server ran out of window while Mint thought it
was above the threshold, and the request stalled. Unreleased bytes count
as received, so manual mode made this easier to hit.
Pull Request #550: Add manual refill of HTTP/2 stream receive windows

35 of 36 new or added lines in 1 file covered. (97.22%)

1 existing line in 1 file now uncovered.

1870 of 2063 relevant lines covered (90.64%)

1503.71 hits per line

Uncovered Changes

Lines Coverage ∆ File
1
95.57
0.02% lib/mint/http2.ex

Coverage Regressions

Lines Coverage ∆ File
1
96.05
-1.32% lib/mint/http1/response.ex
Jobs
ID Job ID Ran Files Coverage
1 963c1d2d24ec052d6470042a26432e5c879509b7-PR-550.1 17 Nov 2026 02:30PM UTC 22
90.64
GitHub Action Run
2 963c1d2d24ec052d6470042a26432e5c879509b7-PR-550.2 17 Nov 2026 02:42PM UTC 22
90.64
GitHub Action Run
Source Files on build 963c1d2d24ec052d6470042a26432e5c879509b7-PR-550
  • Tree
  • List 22
  • Changed 3
  • Source Changed 0
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Pull Request #550
  • PR Base - main (#B8EFB73E...)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc