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 swallowing signals in build_system when running sub-commands #509

Merged
merged 1 commit into from
May 1, 2024

Conversation

GuillaumeGomez
Copy link
Member

Fixes #496.

#[cfg(unix)]
{
if let Some(signal) = status.signal() {
return Err(command_error(input, &cwd, format!("Process received signal {}", signal)));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer that you follow the same behavior as cargo, which is to emit the signal of the process so that the shell sees it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine by me.

@GuillaumeGomez GuillaumeGomez changed the title Stop swalling signals in build_system when running sub-commands Stop swallowing signals in build_system when running sub-commands May 1, 2024
@antoyo antoyo merged commit f557bc4 into rust-lang:master May 1, 2024
11 of 34 checks passed
@GuillaumeGomez GuillaumeGomez deleted the signal-swallowing branch May 1, 2024 14:31
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.

y.sh cargo run swallows the signal emitted by the running process
2 participants