Skip to content

Notinteractive #15184

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

Merged
merged 2 commits into from
May 4, 2023
Merged

Notinteractive #15184

merged 2 commits into from
May 4, 2023

Conversation

KevinRansom
Copy link
Contributor

@KevinRansom KevinRansom commented May 3, 2023

Do not start a ControlledExecution block when the script is executing in --noninteractive mode.

A thread that is executing a ControlledExecution block cannot start a new ControlledExecution block. This is an issue for hosts that use fsi as a library to compile and execute scripts and want to use a ControlledExecution object to halt a threads execution.

Such hosts will typically use --noninteractive because they control the interactions with script processing. So, with this PR, we do not create a ControlledExecution when the script is noninteractive. Which enables the host to create a block and manage interactions.

Adds tests.

@KevinRansom KevinRansom requested a review from a team as a code owner May 3, 2023 22:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants