oxidecomputer / oxidecomputer/vw
cloud: a stale local target dir can cause problems
Open
Nobody has claimed this yet.
bug
cloud
- Dominant language
- Rust
- Stars
- 6
- Forks
- 1
- Avg merge
- 32m
- Merged PRs (30d)
- 5
Description
The following causes issues
- Create cloud environment
a - Build a project using
a, this populates the local target directory. - Delete cloud environment
a - Recreate cloud environment
a - Attempt to run a bench, this fails because locally
vwthinks ip wrappers have already been created, but those wrappers do not exist in the new cloud environment target dir.
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 five-step sequence in the issue, focusing on how the local target directory records cloud-environment state and how bench execution checks it. Confirm the fix by deleting and recreating environment a, then verifying that running a bench succeeds with the new target directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cloud, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100