-
-
Notifications
You must be signed in to change notification settings - Fork 307
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
kube-runtime pulls in two versions of pin-project #709
Comments
|
We already have So we can configure to deny duplicate dependencies. PR to do that is welcomed. |
Do you think we are at a reasonable point to cut a new release at this time? We have a quite sizable CHANGELOG, but there are a couple of outstanding things that are possibly very close (
I can play around with that. |
I'd say the error stuff is relatively fine to split up. Especially if we ensure that any specific error types that we end up exposing to the public API are |
Yeah, I've been trying to refine errors gradually per module (starting from lower level ones), so splitting across releases shouldn't be an issue. Any future refinements shouldn't be related to them. All the higher level modules users use still returns The changelog is overwhelming, so we can add an overview to make the change easier to understand. |
I think |
Summary of changes to
|
Fixed in |
Current and expected behavior
kube-runtime
pulls in two distinct versions ofpin-project
&pin-project-lite
:When using tools like
cargo-deny
to audit dependencies, this requires an exemption like:I imagine this bloats compile times for packages that use
kube-runtime
, though I don't have hard numbers to back up this assumption.Possible solution
I'd love it if we could drop the
snafu
dependency entirely, just to avoid the dependency. I know it offers some conveniences, but these seem surmountable, especially if we usethiserror
for error definitions.thiserror
is already pulled in bykube-client
andkube-core
.Otherwise, it looks like there's a
snafu
v0.7 release in the works that hopefully resolves this?Additionally, it may be valuable to use something like
cargo-deny-action
to audit duplicate/mismatched dependencies, license compliance, etc.Additional context
No response
Environment
n/a
Configuration and features
Affected crates
kube-runtime
Would you like to work on fixing this bug?
maybe
The text was updated successfully, but these errors were encountered: