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

http3 make request future sync #2339

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

Ruben2424
Copy link

Should fix #2322 .

Requires new h3-quinn release and hyperium/h3#249 to be merged.

I removed the http3 specific Resolver trait. Was there a reason for a second one?

I am not familiar with this code base, so please make sure the additional Sync bounds do not break something.

Copy link
Contributor

@NobodyXu NobodyXu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for putting this PR to solve the issue I opened!

I have a bit suggestions:

Cargo.toml Outdated Show resolved Hide resolved
src/dns/resolve.rs Outdated Show resolved Hide resolved
src/async_impl/request.rs Outdated Show resolved Hide resolved
tests/client.rs Outdated Show resolved Hide resolved
@Ruben2424
Copy link
Author

CI is currently failing. At the moment it does not compile with hickory-dns feature enabled.
I check with the master branch and with the hickory-dns the response future is also not Sync

Should this also work with hickory-dns? or just with http3?
I took a quick look at hickory-dns. As far as I understood the crate it is probably not trivial to make their types Sync.

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.

Enable feature h3 in reqwest 0.12.5 adds breaking change: Sync implementation on return future is removed
2 participants