-
Notifications
You must be signed in to change notification settings - Fork 441
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
QUERY_DEPTH attempt to add with overflow #470
Comments
Which version of TRust-DNS Resolver are you using? I just patched a similar issue recently: #469 Also, I just published new versions of the libraries on crates.io, I'm in the middle of writing up the announcement. |
Using 0.8, I see you pushed up 0.9 to crates.io. I can update the branch and see if it still happens! |
Did an update to 0.9, the panic no longer occurs but I'm seeing a lot of errors and no requests going through:
The error messages aren't really saying too much on what's happening. |
I'm sorry, I don't have time right now to dig into your issue. But I recently put together an example that might help you: https://github.com/bluejekyll/trust-dns/blob/master/resolver/examples/global_resolver.rs |
👍 Thanks for the example, no worries, I appreciate all the help! |
Is this issue resolved? |
No, I haven't taken a look at fixing this as c-ares is working for us right now. The issue can still be reproduced on the https://github.com/DarrenTsung/hyper-client-pool/tree/trust-dns |
It looks like tokio-core is being used there. Not sure if that’s an issue. |
Replacing the tokio-core implementation with the global resolver fixed the issue, thanks for the suggestion! |
Awesome! |
Hi, I'm trying to swap out the default DNS resolver in
hyper
withtrust-dns
and I'm seeing this panic when attempting to send out a lot of requests.Full error:
The code in question:
This is reproducible by running the
a_ton_of_notifications()
test on my fork ofhyper-client-pool
which we're using to send notifications.Fork: https://github.com/DarrenTsung/hyper-client-pool/tree/trust-dns.
I'm replacing the DNS resolver with this repo: https://github.com/DarrenTsung/hyper-http-connector/tree/trust-dns-cache-resolver.
Does anyone have any ideas why this might be happening? It might be related to how I implemented trust-dns resolver?
I have a c-ares implementation that works, but it would be great to use trust-dns for this as we use it elsewhere in our notification pipeline!
The text was updated successfully, but these errors were encountered: