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.
The
main
branch of loftee causes a ton of error logging messages when running on GRCh38.Example here (similar errors being throw 27000+ times during processing of one variant subset)
There is a separate branch which we can use instead, with an updated version of the plugin files, see konradjk/loftee#84 (and other similar issues)
The path to copy the plugin files to contains a
*
-This copy works for both situations when building the image, but doesn't resolve hard-coding like this
As of today I don't believe there's a way to set an env variable to the result of a RUN command, otherwise this could be used:
ls -l ${MAMBA_ROOT_PREFIX}/share/ | grep ensembl | awk '{ print $9}'
this could be used in setting the path in the production-pipelines job?
... but this looks really heavy handed