-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
bugfix: ZipperBams should consume any remaining mapped reads #929
Conversation
So that pipes do not cause failure when unread data exists in bash strict mode
Codecov ReportPatch coverage:
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## main #929 +/- ##
==========================================
- Coverage 95.61% 95.60% -0.02%
==========================================
Files 126 126
Lines 7303 7305 +2
Branches 498 517 +19
==========================================
+ Hits 6983 6984 +1
- Misses 320 321 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
|order, and reads with the same name are consecutive (grouped) in each input""".stripMargin | ||
) | ||
} | ||
|
||
out.close() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would probably be kind to move out.close()
above so that the output BAM is at least somewhat valid/intact?
So that pipes do not cause failure when unread data exists in bash strict mode.
@jacarey