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

Unify use of spawn_child_async in click handlers #594

Merged
merged 3 commits into from
Apr 21, 2020

Conversation

Celti
Copy link
Contributor

@Celti Celti commented Apr 13, 2020

This follows up #530 by using crate::subprocess::spawn_child_async for
all click handlers that spawn such processes, to unify handling of stdin
and stdout and prevent broken pipe errors such as #420 in all cases.

This also uses spawns such commands with sh -c to making handling
environment and quoting more flexible.

This follows up greshake#530 by using `crate::subprocess::spawn_child_async` for
all click handlers that spawn such processes, to unify handling of stdin
and stdout and prevent broken pipe errors such as greshake#420 in all cases.

This also uses spawns such commands with `sh -c` to making handling
environment and quoting more flexible.
All uses of `subprocess::parse_command` were removed in b57d1dd.
@ammgws
Copy link
Collaborator

ammgws commented Apr 13, 2020

LGTM

Did you test it as well?

@Celti
Copy link
Contributor Author

Celti commented Apr 13, 2020

Yes, I did — specifically the sound block as referenced in #420 but I also deliberately searched for and attempted to trigger the bug in other blocks.

@ammgws ammgws merged commit 98f712a into greshake:master Apr 21, 2020
@ammgws
Copy link
Collaborator

ammgws commented Apr 21, 2020

Thanks!

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.

None yet

2 participants