-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Documentation for header_read_timeout
is incomplete
#3567
Comments
The example Timer implementation for |
I agree with all of that. I think the three points all still stand, as opportunities for improvement. Will eventually give it a shot if nobody beats me to it. |
That's fair. The doc for |
There is an implementation available in hyper-util, maybe this can be mentioned in the documentation. |
The docs for hyper::rt will be added in hyperium/hyperium.github.io#121. Will close this issue since we're also tracking it in #3411, and Thanks for the report @jorendorff ! |
The problem was caused by hyperium/hyper#3567 Adding a timer to our server instance solved the problem and we can now send requests to the router. :)
Three mini-issues here:
Documentation for
.header_read_timeout()
doesn't mention that it requires.timer()
or it'll panic.The example in the docs for
http1::Builder
usesheader_read_timeout
withouttimer
. It's not meant as complete running code, but still, it's weird that if you did try to use it, you'd panic.No pointer to an implementation of Timer for tokio. I found a full implementation in a doc-comment, but unfortunately that's a private module.
The text was updated successfully, but these errors were encountered: