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

conda not activated at nextclade if standard profile is used #56

Open
2 tasks done
MarieLataretu opened this issue Apr 18, 2023 · 1 comment
Open
2 tasks done
Assignees

Comments

@MarieLataretu
Copy link
Collaborator

MarieLataretu commented Apr 18, 2023

no problem with -profile conda,local, but with missing -profile parameter

  • check if reproducible
  • pangolin also affected?
@MarieLataretu MarieLataretu self-assigned this Apr 18, 2023
@MarieLataretu
Copy link
Collaborator Author

Conda/mamba check via profile name -> only check for "conda" and "mamba", not the standard profile -> conda is set to null with the standard profile

It seems like the conda directive doesn't need to be set to null with nextlfow > 22.10.1 (see nf-core modules)

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

No branches or pull requests

1 participant