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

Stop forwarding SIGINT to child processes #322

Merged
merged 1 commit into from
Jun 20, 2022

Conversation

gibfahn
Copy link
Contributor

@gibfahn gibfahn commented Jun 6, 2022


Commits (oldest to newest)

22c287a Stop forwarding SIGINT to child processes

Since we handle os.Interrupt but no longer forward it to child
processes, this commit also removes platform-specific handling for
Windows, preferring to use child.Process.Kill() in all cases.

Fixes #307.


Since we handle os.Interrupt but no longer forward it to child
processes, this commit also removes platform-specific handling for
Windows, preferring to use child.Process.Kill() in all cases.

Fixes bazelbuild#307.
@gibfahn
Copy link
Contributor Author

gibfahn commented Jun 18, 2022

@fweikert any chance you could take a look? Hopefully a pretty straightforward change.

@fweikert fweikert self-requested a review June 20, 2022 13:08
@fweikert
Copy link
Member

Thank you! Looks good to me.

@fweikert fweikert merged commit 70694fe into bazelbuild:master Jun 20, 2022
@gibfahn gibfahn deleted the signal-handling branch June 25, 2022 19:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Go bazelisk causes double-SIGINT in "bazel run"
2 participants