panic with 'Source should be ready'

[Noah-Kennedy]

An invocation of cargo outdated -w -R is currently failing consistently for me with the following message:

thread 'main' panicked at 'Source should be ready', /home/noah/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cargo-outdated-0.13.1/src/cargo_ops/temp_project.rs:394:18

This happens for any repo I have tried that uses a specific third-party sparse-only registry we currently run internally (a forked version of alexandrie which serves sparse).

I can reproduce this consistently from my laptop, however I do not have an MCRE that I can share on here.

As the author of another (this one open source) sparse-only registry that we are going to be migrating to soon, I can try and use that to get an MCRE later if you'd like.

[Noah-Kennedy]

Link to error: https://github.com/kbknapp/cargo-outdated/blob/master/src/cargo_ops/temp_project.rs#L394C21-L394C21

[Noah-Kennedy]

I have yet to try this with other third party or sparse-only registries.

[Noah-Kennedy]

@kbknapp I don't quite follow what's going on in this code segment. What's the expected state of things at the time that this panic occurs, and what is going wrong here exactly that cargo-outdated doesn't like?

[MikeDevresse]

I have the same issue and it seems that commenting the code fragment that you mentioned solve the issue. It seems that the block_until_ready doesn't do its job and that the invalidate_cache is not necessary because the repository is updated anyway.

[hseeberger]

Same issue here.