LukeMathWalker / LukeMathWalker/cargo-chef
Does not correctly handle cross-workspace dependencies.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 146
- PR merge metrics
- No merged PRs in 30d
Description
I know, I have a most complicated build that ever existed... :D
For complicated reasons, that I can't get into RN my project structure is more or less:
root
client
client-lib-x
api
server
The client and server are a different workspace. But they both include the api as path = "../api".
So I'm running cargo-chef inside both server and client, but then cargo chef cook gets totally confused, and says:
Caused by:
Unable to update /app/app/api
Caused by:
failed to read `/app/app/api/Cargo.toml`
Even though path ... should be ... Hmmm... /app/api/Cargo.toml . Seems like some path concatenation somewhere where wrong WRT ...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported layout with separate client and server workspaces that both reference api through a relative path. Start with cargo chef cook and inspect how the referenced Cargo.toml path is resolved when the dependency contains ... Done means both workspaces handle the api dependency without resolving it to the incorrect /app/app/api location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100