Watchdog feature for resources
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Summary of the new feature / enhancement
We don't want a single resource blocking completion of a configuration. Timeouts aren't predictable as the time something takes can differ on different systems and also networks.
Proposed technical implementation details (optional)
DSC engine should have a built in watchdog that will timeout after some predefined time (can be settable via parameter, but maybe default to 5 minutes?). Basically, a resource that does not emit anything to stderr or stdout within the watchdog timeout will cause dsc to kill the resource and report a timeout. Anything sent to stderr (progress, trace, maybe we can have a generate heartbeat message if needed) will reset the watchdog.
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 with the DSC engine's resource execution path and the dsc command described in the issue. Determine how resource stdout and stderr are handled, then define the timeout and parameter behavior before implementing it. Done means a silent resource is killed and reported as timed out, while output resets the watchdog.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100