mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[GH-ISSUE #2223] just no-default-features fails with an ICE using latest nightly #928
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#928
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 @japaric on GitHub (May 29, 2024).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2223
Describe the bug
What the title says
To Reproduce
just no-default-featuresExpected behavior
Command should succeed.
System:
1.80.0-nightly (da159eb33 2024-05-28)Version:
Crate: all
Version:
107635c6c5Additional context
Observed in one of the CI jobs running for PR #2222 . This failure will likely prevent all PRs from being merged. I would suggest pinning all uses of a nightly toolchain, e.g.
nightly-2024-05-15, to prevent transient breakage in nightly leaking into CI@japaric commented on GitHub (May 29, 2024):
reduced version:
cargo build -p hickory-server --all-targets --benches --examples --bins --tests --no-default-featuresthis is a bug in rustc that has already been reported several times, e.g.
rust-lang/rust#125707. PRrust-lang/rust#125493should fix it