Skip to content

Conversation

Firestar99
Copy link
Member

@Firestar99 Firestar99 commented Oct 8, 2025

In #116 we're hit problems where the dylib still exists but the cargo project was deleted. Currently, the install process is skipped if just the dylib file exists. After the install we call cargo metadata to resolve the toolchain version, which will error if the project was deleted. With this PR, we also detect the project being deleted and do a rebuild, not just when the dylib is missing.

Long-term it would probably be better to just store the toolchain version in a metadata json or text file, and not reresolve it each time. With #117 currently refactoring much of cargo-gpu, I think we'll wait for that to complete before implementing it.

closes #116

@Firestar99 Firestar99 requested review from schell and tombh October 8, 2025 15:15
@Firestar99 Firestar99 enabled auto-merge (squash) October 8, 2025 15:28
@tombh
Copy link
Collaborator

tombh commented Oct 8, 2025

I was following your #116, I've seen similar weirdness before and just deleted everything to move on. It's great you spent some proper time to look into it.

@Firestar99 Firestar99 merged commit 0982968 into main Oct 8, 2025
6 checks passed
@Firestar99 Firestar99 deleted the cache-resiliance branch October 8, 2025 15:38
@Firestar99
Copy link
Member Author

There's still #72 which is the main kind of error I get from cargo-gpu in my project. Though of the two racing build scripts one usually fails early and you can just rerun it and it works.

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

Successfully merging this pull request may close these issues.

graphite CI breaking

2 participants