hyperlight-dev / hyperlight-dev/hyperlight-wasm
Don't reset $CARGO_HOME when building wasm_runtime
Open
Nobody has claimed this yet.
lifecycle/confirmed
- Dominant language
- Rust
- Stars
- 728
- Forks
- 39
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 23
Description
When hyperlight_wasm builds wasm_runtime, it currently resets all Cargo environment variables. We should exempt any that are likely actually the user's configuration, including $CARGO_HOME.
Contributor guide
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
Start in src/hyperlight_wasm/build.rs around line 115, where building wasm_runtime resets Cargo environment variables. Trace which variables are cleared and identify user configuration that should be preserved, including CARGO_HOME. Done means the build no longer resets those user-provided Cargo settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100