Cannot compile due to chrono issue about kube HOT 7 CLOSED

That's a good point, thank you. I'll bump the entry for it.

from kube.

try upgrading chrono first, we did do some stuff with chrono to avoid new lint warnings

from kube.

How can I upgrade chrono if it's being pulled automatically by both crates?

from kube.

I assume you have a pin for it in your lock file. The chrono::TimeDelta struct does exist in the last version.

from kube.

so I think what happens here is that chrono::TimeDelta was missing in chrono 0.4.33 (a semver compatible version) and added in 0.4.34. So when you upgrade kube/k8s-openapi cargo doesn't force you to also upgrade chrono because chrono have not indicated they have added anything by making a semver-minor (and we accidentally started relying on a new feature without knowing it was a new feature).

If you run cargo update chrono it will fix the issue and bump the pin in your lockfile (without needing an explicit dependency on chrono in your Cargo.toml).

from kube.

Thank you, completely forgot about the lockfile

from kube.

kube-client specifies,

chrono = { version = "0.4.32", default-features = false }

As @clux says above, TimeDelta isn't added until 0.4.34.

kube-client could just depend on 0.4.34 — it isn't compatible with 0.4.32, so specifying that as a version doesn't make much practical sense as it'll never work, and if you specify 0.4.34 then cargo will just do the right thing & realize the locked version will never work. I.e., you should never need to remember the lockfile.

It'd be nice if kube-rs would just consider this a bug, to avoid all downstream users from having to manually handle this.

(chrono here is pre-1.0, so backwards-compatible versions — i.e., adding a feature — wouldn't bump the minor. Cargo's consideration of 0.x.y versions is slightly different than the SemVer.org spec.)

from kube.