-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Fix Cargo warning about unused sparse configuration key #11930
Conversation
When doing a credential lookup, Cargo deserializes the registry configuration and detects the registries.crates-io.protocol key as unused and issues a warning. This fixes the issue by adding the field to the struct
r? @weihanglo (rustbot has picked a reviewer for you, use r? to override) |
#[serde(rename = "protocol")] | ||
_protocol: Option<String>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there something we can do to avoid running into this issue in the future?
@bors r+ |
Fix Cargo warning about unused sparse configuration key When doing a credential lookup, Cargo deserializes the registry configuration and detects the `registries.crates-io.protocol` key as unused and issues a warning: ``` warning: unused config key `registries.crates-io.protocol` in [..] ``` This fixes the issue by adding the field to the `RegistryConfig` struct.
💔 Test failed - checks-actions |
@bors retry |
Fix Cargo warning about unused sparse configuration key When doing a credential lookup, Cargo deserializes the registry configuration and detects the `registries.crates-io.protocol` key as unused and issues a warning: ``` warning: unused config key `registries.crates-io.protocol` in [..] ``` This fixes the issue by adding the field to the `RegistryConfig` struct.
💔 Test failed - checks-actions |
@bors r+ |
💡 This pull request was already approved, no need to approve it again. |
Fix Cargo warning about unused sparse configuration key When doing a credential lookup, Cargo deserializes the registry configuration and detects the `registries.crates-io.protocol` key as unused and issues a warning: ``` warning: unused config key `registries.crates-io.protocol` in [..] ``` This fixes the issue by adding the field to the `RegistryConfig` struct.
☀️ Test successful - checks-actions |
Update cargo 17 commits in 0e474cfd7b16b018cf46e95da3f6a5b2f1f6a9e7..7bf43f028ba5eb1f4d70d271c2546c38512c9875 2023-03-31 23:15:58 +0000 to 2023-04-10 16:01:41 +0000 - docs(pkgid): Consistently use @ (rust-lang/cargo#11956) - Fix credential token format validation. (rust-lang/cargo#11951) - Validate token on publish. (rust-lang/cargo#11952) - Clarify docs on `-C` that it appears before the command. (rust-lang/cargo#11947) - Add `try_canonicalize` and use it over `std::fs::canonicalize` (rust-lang/cargo#11866) - Fix typo (rust-lang/cargo#11944) - docs(changelog): Change wording about auto-fix message (rust-lang/cargo#11943) - Update home repo URL (rust-lang/cargo#11941) - doc(changelog): `[env]` is a table, not a stable (rust-lang/cargo#11942) - Stop using UncanonicalizedIter for QueryKind::Exact (rust-lang/cargo#11937) - Don't query permutations of the path prefix. (rust-lang/cargo#11936) - Fix typo in variable name (rust-lang/cargo#11931) - Fix Cargo warning about unused sparse configuration key (rust-lang/cargo#11930) - Switch benchsuite to the index archive. (rust-lang/cargo#11933) - Update git2 (rust-lang/cargo#11928) - Publish docs: Clarify requirements about the state of the index after publish. (rust-lang/cargo#11926) - Call out the differences between the index JSON and the API or metadata. (rust-lang/cargo#11927)
When doing a credential lookup, Cargo deserializes the registry configuration and detects the
registries.crates-io.protocol
key as unused and issues a warning:This fixes the issue by adding the field to the
RegistryConfig
struct.