You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to build a crate, but ran into an issue where a dependency was corrupted. I then tried to cargo clean the project, thinking that would fix it, but it didn't. I had to nuke my WSL and reinstall it to get the crate to build, losing a lot of time and effort.
Steps
No response
Possible Solution(s)
cargo clean should also apply to dependencies, and not just the direct project.
Notes
No response
Version
No response
The text was updated successfully, but these errors were encountered:
Assuming “downloaded crates” refer to downloaded source code resides under $CARGO_HOME/registry/{crate,src}, the design is tracked in #13060. Going to close this in favor of that. Please comment below if there is any reason keeping this issue open. Thank you.
Thanks for the pointers - I wish I'd have found those links sooner... I'm not sure my issue is directly related to the gc issue though - I would like to clean my dependencies entirely, not gc them depending on cache age.
Unlike some other build systems, dependency source is kept in a global cache while cargo clean is focused on your local cache. Think of the GC feature as a way for managing the global cache. The interface for doing so is not yet defined.
Problem
I tried to build a crate, but ran into an issue where a dependency was corrupted. I then tried to
cargo clean
the project, thinking that would fix it, but it didn't. I had to nuke my WSL and reinstall it to get the crate to build, losing a lot of time and effort.Steps
No response
Possible Solution(s)
cargo clean
should also apply to dependencies, and not just the direct project.Notes
No response
Version
No response
The text was updated successfully, but these errors were encountered: