canonical / canonical/multipass
Pass timeout from daemon to backend operations
- Dominant language
- C++
- Stars
- 9.2k
- Forks
- 828
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 44
Description
Currently there are [places](https://github.com/canonical/multipass/blob/0c58deb74c38bfc364311cae38b4b14b3646fec9/src/platform/backends/lxd/lxd_virtual_machine.cpp#L189) where we should be passing the timeout from the daemon when doing backend operations. Another candidate for this would be https://github.com/canonical/multipass/pull/2935.
Contributor guide
Research direction
Start with src/platform/backends/lxd/lxd_virtual_machine.cpp around line 189, then review the timeout flow in pull request #2935. Trace which daemon-triggered backend operations are in scope and identify how completion should demonstrate that the daemon timeout is propagated consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100