Conversation
🐳 Expected TagsSome Dockerfiles have been modified in this PR. New tags are expected to be deployed.
|
MattWellie
approved these changes
Feb 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the out of date Picard image from v2.27.4 (released June 2022) to the latest release v3.4.0
Of particular interest is this bugfix:
I don't fully comprehend the logic here, but in the PR body
Reviewing this PR made me realise that
MAX_RECORDS_IN_RAMdoes NOT have a hardcoded default of 500000 like the GATK docs would have you believe. If not specified, the max records value is derived from system information. Although this case is using 10x the RAM we usually use, it still may explain why our jobs have been failing.bookworm-slimand the Micromamba install to the latest