liquidmetal-dev / liquidmetal-dev/flintlock
Report failure message via the gRPC API
Open
Nobody has claimed this yet.
area/api
good first issue
help wanted
kind/feature
priority/important-soon
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 73
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 30
Description
**Describe the solution you'd like:**
If the `Get` returns a microvm with a status of failed then we should have an failure reason/message
**Why do you want this feature:**
This is so we can report the error in the capmvm machine controller.
**Anything else you would like to add:**
[Miscellaneous information that will assist in solving the issue.]
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 by tracing the gRPC API's Get entry point and how a failed microVM status is represented. Done means Get exposes a failure reason or message that the capmvm machine controller can report; the issue names no specific files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100