Local cargo index is significantly outdated

[LJNeon]

Describe the bug With the "Use Local Cargo Index" setting enabled, the extension provides seriously outdated crate versions. Disabling that setting resolves the issue, but re-enabling it does solve the issue. Uninstalling and reinstalling the extension also doesn't fix.

Expected behavior If there's a local index enabled by default, it should be kept up-to-date.

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS] Windows 10
• Version [e.g. 22] 21H1

[LJNeon]

If this helps diagnose the issue: I haven't opened VSCode on that computer in months. The local index versions appear to be from around when I last opened VSCode.

[sardobi]

I'd been putting up with outdated dependency info for many months - this issue helped me work around it, thanks.

If disabling "Use Local Cargo Index" makes the problem go away, is there any reason not to make it the default?

[ivan]

I think my local Cargo index stopped updating because I started using cargo only with CARGO_UNSTABLE_SPARSE_REGISTRY=true.

Also, if I disable "Crates: Use Local Cargo Index", I get a lot of "API rate limit exceeded" from crates.io.

My workaround is

# Update the local crates.io registry, just for the Crates vscode extension.
# There is no subcommand to update the local registry, so we just try to install
# something that fails to install.
#
# https://github.com/serayuzgur/crates/issues/154
# https://github.com/serayuzgur/crates/issues/81
# https://github.com/rust-lang/cargo/issues/3377
#
# cargo must be run here without `CARGO_UNSTABLE_SPARSE_REGISTRY=true`
/run/current-system/sw/bin/cargo install lazy_static || true

[novedevo]

Sparse registry was stabilized in Rust 1.68, and will become the default in 1.70, so this error is likely to occur more and more often. I have sparse registry enabled for the performance benefits, and have been getting a lot of rate limit exceeded messages.

[jnicholls]

I worked around this by changing the setting Local Cargo Index Hash to point to my CARGO_UNSTABLE_SPARSE_REGISTRY=true directory which is named index.crates.io-<hash> (as opposed to the github.com-<hash> directory used with the legacy git crates.io protocol). Look under the ~/.cargo/registry/cache/ directory for your cache directory name.

[serayuzgur]

Since there are many issues going related with this, we have our own index server now. No more local checks with v0.6.0