nextflow-io / nextflow-io/nextflow
new feature: make sure conda env is intact for usage
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
New feature
Is it possible to have a way to verify the conda environment is intact before launching the pipeline? There are times that the creation of the conda environments fail without (me) notice, the next time i launch, nextflow would assume the env is created and go along with the broken environments. If the env is used in the modules with error ignore, it would take ages for people to find out that failure of the error ignre step is due to conda
Use case
Make sure conda env is indeed correctly created
Suggested implementation
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the conda environment creation and pipeline-launch paths, then determine how an intact environment can be checked before launch. Done means a failed or incomplete conda environment is detected before the pipeline proceeds, with a useful failure signal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100