Skip to content
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

Allow to config h2 max concurrent reset streams. #2535

Merged
merged 3 commits into from
May 13, 2021

Conversation

boxdot
Copy link
Contributor

@boxdot boxdot commented May 4, 2021

Setting streams to 0 makes h2 work on wasm platforms without Instant::now implementation.

Related to:

@boxdot boxdot force-pushed the config-max-reset-streams branch 2 times, most recently from 171aea1 to d231963 Compare May 4, 2021 07:44
@boxdot boxdot force-pushed the config-max-reset-streams branch from d231963 to 7ca0433 Compare May 5, 2021 17:38
src/proto/h2/client.rs Outdated Show resolved Hide resolved
Setting streams to 0 makes h2 work on wasm platforms without a
`Instant::now` implementation. The default value if derived from
the default value in the h2 crate.
@boxdot boxdot force-pushed the config-max-reset-streams branch from 75b3d17 to aba1761 Compare May 7, 2021 15:59
@seanmonstar
Copy link
Member

I've got #2548 going to fix the weird failure on nightly.

@seanmonstar seanmonstar enabled auto-merge (squash) May 13, 2021 01:16
@seanmonstar seanmonstar merged commit b9916c4 into hyperium:master May 13, 2021
BenxiangGe pushed a commit to BenxiangGe/hyper that referenced this pull request Jul 26, 2021
…erium#2535)

Setting streams to 0 makes h2 work on wasm platforms without a
`Instant::now` implementation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants