Ricky Hosfelt

Hi @frederikhors thanks for this issue! This is because `uuidv07` isn't explicitly in the `[features]` section of the `Cargo.toml` but is mapped to the `uuid` package here: `uuidv07 = {...

No worries, looks like just `cargo-outdated` is parsing this slightly wrong. In the `diesel` changelog.md; however, it looks like the next release will rename this to`uuid` and drop support for...

I have a fix for this in https://github.com/deg4uss3r/cargo-outdated/commit/97a2e2979576e6efe02369b0f4dfec3571402e29 it is working locally for me :)

`cargo-outdated` does build a similar project in temp, is this still happening with `0.9.10`? If so can you provide some more information: * Which OS and Version are you running...

These appear to be network timeouts, are you behind a proxy? `cargo-outdated` should have `$HTTPS_PROXY` set your communicate with the pass through to the external network. If not what details...

Yeah looks like you did get it with the crates.io outage at first with this error: > `Caused by: failed to get 200 response from `https://crates.io/api/v1/crates/core-foundation/0.6.4/download`, got 502` However, you...

@cmdln Any additional information you could give might be helpful, I cannot recreate this and from the errors I'm stumped. @application-developer-DA could you also try running with `RUST_LOG=debug`? Try this...

@cmdln can you try with `export RUST_LOG=debug` as well? Again do this in a smaller repository it will output a lot of stuff (e.g. a toml containing only something like`rand...

I don't think that's the underlying error here, but I could definitely be wrong! Did you try running with `RUST_LOG=debug` to see if there's some low level network errors that...

That's interesting.. @application-developer-DA could you post the `Cargo.toml` that reproduces this and the other error for you?