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

Handle broken pipes #30

Merged
merged 3 commits into from
Jul 15, 2022
Merged

Handle broken pipes #30

merged 3 commits into from
Jul 15, 2022

Conversation

ressy
Copy link
Member

@ressy ressy commented Jul 14, 2022

If igseq's stdout is closed (such as from another process working with its output) this will try to gracefully handle the closed pipe, including for an igblastn subprocess. Fixes #20. I think.

Make the main function handle broken pipes and cleanup; fixes for pipe
handling for igblast context manager and subprocess
This reaches back out from the unit testing to run a bash script to
check this behavior.  Not sure if this would scale reasonably if there
are many more of these, but at least it's tested somewhere (and this
test currently fails on dev but should pass here)
@ressy ressy merged commit 5cf4833 into dev Jul 15, 2022
@ressy ressy deleted the fix-20-broken-pipes branch July 15, 2022 14:03
ressy added a commit that referenced this pull request Jul 18, 2022
@ressy ressy mentioned this pull request Sep 17, 2022
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.

Broken pipes should be handled quietly in command-line interface
1 participant