Every build printed unused variable: h3 from vendor/hickory-dns/hickory-resolver/src/name_server.rs. The variable was gated on __tls instead of __h3, so builds with TLS but without HTTP/3 (ours) created it and never used it.
hickory's main already has #[cfg(feature = "__h3")] on that line; release/0.26, which our copy comes from, doesn't yet. VENDORED.md's Changes section now lists it, so a re-vendor past the fix drops it.
Checked: cargo check -p hickory-resolver has no warnings, and the vendored crates also build cleanly with h3-ring, quic-ring, https-ring and tls-ring on.
Every build printed `unused variable: h3` from `vendor/hickory-dns/hickory-resolver/src/name_server.rs`. The variable was gated on `__tls` instead of `__h3`, so builds with TLS but without HTTP/3 (ours) created it and never used it.
hickory's `main` already has `#[cfg(feature = "__h3")]` on that line; `release/0.26`, which our copy comes from, doesn't yet. VENDORED.md's Changes section now lists it, so a re-vendor past the fix drops it.
Checked: `cargo check -p hickory-resolver` has no warnings, and the vendored crates also build cleanly with `h3-ring`, `quic-ring`, `https-ring` and `tls-ring` on.
NameServer::new created its h3 connection state under the __tls feature
instead of __h3, so every build with TLS and without HTTP/3 (ours)
warned about an unused variable. hickory's main has the corrected cfg;
release/0.26, which this copy comes from, doesn't yet. VENDORED.md
records the change so a re-vendor past it drops it.
Checked with and without HTTP/3: no warnings either way.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Every build printed
unused variable: h3fromvendor/hickory-dns/hickory-resolver/src/name_server.rs. The variable was gated on__tlsinstead of__h3, so builds with TLS but without HTTP/3 (ours) created it and never used it.hickory's
mainalready has#[cfg(feature = "__h3")]on that line;release/0.26, which our copy comes from, doesn't yet. VENDORED.md's Changes section now lists it, so a re-vendor past the fix drops it.Checked:
cargo check -p hickory-resolverhas no warnings, and the vendored crates also build cleanly withh3-ring,quic-ring,https-ringandtls-ringon.