Add RFC for hosting API bounded waits#409
Open
SufficientDaikon wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This RFC proposes adding bounded-wait timeout support to the PowerShell hosting API — two new public API members:
PSInvocationSettings.Timeout(TimeSpan, defaultInfiniteTimeSpan)PowerShell.Stop(TimeSpan timeout)These allow C# host applications to enforce deadlines on script invocation and pipeline stop operations. The default
InfiniteTimeSpanpreserves all existing behavior — the feature is purely opt-in with zero overhead when not used.Reference implementation: PowerShell/PowerShell#27027
Interactive docs: https://ps-bounded-wait-docs.pages.dev/
This change is