"Could not find requested crate" even for a direct dependency

Question

"Could not find requested crate" even for a direct dependency

Minoru opened this issue 2 years ago · comments

Alexander Batischev commented 2 years ago

$ cargo new reproducer
     Created binary (application) `reproducer` package
$ cd reproducer
$ cargo add fastrand@1.8.0
    Updating crates.io index
      Adding fastrand v1.8.0 to dependencies.
$ cargo crev crate diff fastrand -- -ruN
    Updating crates.io index
Could not find requested crate. Try `-u` if the crate is not a dependency.

The expected output is a diff between fastrand 1.7.0 and 1.8.0 (because 1.7.0 is the latest reviewed version at the moment).

I bisected this to commit 68656a3 which added -u.

Please let us know:
- Which version are you using: cargo-crev 0.23.2
- How did you install crev: via cargo install
- What OS/platform are you running on: Debian 11.4

Dawid Ciężarkiewicz · Answer 1 · Tue Jul 26 2022 06:44:10 GMT+0800 (China Standard Time)

Hmm... it works here with 0.23.1 ...

Dawid Ciężarkiewicz · Answer 2 · Tue Jul 26 2022 06:50:01 GMT+0800 (China Standard Time)

Interesting. A workaround is to:

cargo crev crate diff -u fastrand -- -ruN

but I'll need to look into why non-unrelated codepaths can't look it up.

It does show up in cargo crev verify...

Alexander Batischev · Answer 3 · Tue Oct 11 2022 16:34:59 GMT+0800 (China Standard Time)

Yup, adding -u works. I was hoping you'll spot the problem immediately, but since you can't even reproduce it, I'll find time this weekend to step through it with a debugger and see what's going on.

Dawid Ciężarkiewicz · Answer 4 · Wed Oct 12 2022 03:50:38 GMT+0800 (China Standard Time)

I think this should be already fixed. See a6f1f12

Alexander Batischev · Answer 5 · Thu Oct 13 2022 01:39:48 GMT+0800 (China Standard Time)

Sorry, it's GitHub acting up. I commented via email on 26th of July, but it took GitHub 1.5 months to display the comment ._.