Closed epage closed 3 years ago
Is it reproducible?
Is it possible that some other process was modifying the repo at the same time?
Oh I see, you're using the latest published version, where Index
uses checkout-based access. The crates-index crate is moving to use bare-repo-based access, which is closer to what Cargo uses. In the latest published version that's BareIndex
. It's going to be the only implementation going forward.
That seemed to work. Look forward to the new version since the docs point people to Index
without clear distinction of when to not use it (ever?).
https://github.com/killercup/cargo-edit/pull/484/checks?check_run_id=3445952771
I'm a bit baffled at why this would happen. We've done a build, so the registry should be populated. This a problem with index vs workspace and concurrent updating of workspace? I think I saw that the new version will be bypassing the workspace completely, which would remove the need for adding extra locks.