elixir-mint / mint / 70b522ee80a69f3c44f899b6c807b89a3ad75b16-PR-481 / 1
88%
main: 88%

LAST BUILD BRANCH: next_body_chunk
DEFAULT BRANCH: main
Ran
Files 20
Run time 0s
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
coverage: 88.125% (+0.3%) from 87.808%
70b522ee80a69f3c44f899b6c807b89a3ad75b16-PR-481.1

Pull #481

github

ericmj 
Track advertised receive window synchronously in initiate/5

Streams opened before the server's SETTINGS ACK arrived were reading
their initial receive window from `conn.client_settings`, which still
held library defaults at that point. If the user advertised a stream
window smaller than the default (e.g. `initial_window_size: 65_535`),
the stream struct tracked the 4 MB default locally while the server
respected the 65_535 we sent in SETTINGS. The client's remaining
window never dropped to the refill threshold, stream-level
WINDOW_UPDATE frames never fired, and the connection stalled once the
server exhausted its per-stream send window.

Mirror the advertised `client_settings_params` into
`conn.client_settings` during `initiate/5` — the sender already knows
what it committed to and doesn't need to wait for the ACK to act on
it. Add a regression test that opens a stream before the ACK round
trip and asserts the stream struct reflects the advertised value.

Also rename `receive_window` to `receive_window_remaining` so the
peak/remaining distinction is clear at the call site, and document
that `:receive_window_update_threshold` is shared between the
connection and per-stream windows (so windows at or below the
threshold refill on every DATA frame).
Pull Request #481: Raise default HTTP/2 receive windows and batch HTTP/2 receive-window refills

1358 of 1541 relevant lines covered (88.12%)

246.94 hits per line

Source Files on job 70b522ee80a69f3c44f899b6c807b89a3ad75b16-PR-481.1