Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there a way to use an old cache but force an update to the cache when saving? #192

Open
Imberflur opened this issue Mar 1, 2024 · 1 comment

Comments

@Imberflur
Copy link

The main way I know to force an update to the cache is changing the prefix-key, but AFAIK that will start from scratch instead of reusing an old cache entry.

I'm trying to debug why some dependencies are being rebuilt and it would be a quicker debug process if I could reuse the current cache when updating the cache (ofc if I'm able to identify the issue, I would want to do a final test from a clean slate to make sure things aren't just working due to the cache built up during debugging).

@Imberflur
Copy link
Author

Looking at the source for how the restore key vs the full cache key are computed, it seems like I may be able to edit a comment in .cargo/config.toml as a workaround for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant