Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Watchdog feature for resources #655

Open
SteveL-MSFT opened this issue Feb 20, 2025 · 0 comments
Open

Watchdog feature for resources #655

SteveL-MSFT opened this issue Feb 20, 2025 · 0 comments
Labels
Issue-Enhancement The issue is a feature or idea Needs Triage

Comments

@SteveL-MSFT
Copy link
Member

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.

@SteveL-MSFT SteveL-MSFT added Issue-Enhancement The issue is a feature or idea Needs Triage labels Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Enhancement The issue is a feature or idea Needs Triage
Projects
None yet
Development

No branches or pull requests

1 participant