mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[GH-ISSUE #1832] [BUG] Build failure with only feature dns-over-https #785
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#785
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @NobodyXu on GitHub (Nov 17, 2022).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1832
cargo check --no-default-features --features dns-over-httpsfailed with:I found this when running
cargo hack check --feature-powerset.System:
This bug does not depend on specific system configure to reproduce.
Version:
Crate: proto
Version: 0.22.0
Additional context
This bug is originally found in https://github.com/cargo-bins/cargo-binstall/pull/538 and https://github.com/cargo-bins/cargo-binstall/pull/430
It can be reproduced on GHA mac (x86-64)/windows/ubuntu whenever trust-dns is enabled and also on my M1 mac.
@NobodyXu commented on GitHub (Nov 17, 2022):
NOTE that enabling
dns-over-native-tlsalso failed:@djc commented on GitHub (Nov 20, 2022):
It's a little unclear to me what's actually the purpose here. As I see it, the
dns-over-httpsfeature by itself isn't particularly useful, and is mostly used as a common subset fordns-over-https-rustlsanddns-over-https-native-tls. So why should we fix this?