Job is stuck in provisioning if launch fails
Open
- Dominant language
- Go
- Stars
- 22
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
I attempted a `cloudexec launch` but it failed due to there not being an `./input` directory present locally.
`cloudexec status` shows the job provisioning even though a droplet was never created.
Contributor guide
Assessment
This issue has not been assessed yet.