-
Notifications
You must be signed in to change notification settings - Fork 21
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
plugin/nf-validation error with old version of Nextflow #293
Comments
@pecko-g is there any way for you to ask the system administrators to update nextflow? This might be the easiest fix. |
It should be possible to install a local copy of Nextflow for your user account:
This will download the Nextflow executable file to your current directory. You can then put the executable file in your home |
Thank you @nebfield, that worked! Is there a similar solution for installing Singularity or Docker? I don't have permission to use sudo. I thought I could run the pipeline with Conda, but it's telling me it can't create an environment...
|
Unfortunately both docker and singularity require administrator access to set up properly. Normally HPC sysadmins are happy to help you with this kind of thing. Perhaps you could try installing a user version of miniconda with the same approach you used to install nextflow. |
Thank you very much again! It seems we're getting closer. This time it managed to create the environment. Now it says it's missing the 'pgscatalog_utils' module. Maybe I can download it manually into the right folder? Would that be one of the two?
|
Could you test with:
This should reset your installation. We did a new release last Friday but found some problems over the weekend, so we've withdrawn it, which might have caused some problems for you. |
I got the same error again. |
I'm not sure how to fix your local environment, sorry. The workflow runs OK with the conda profile in our test suite. You should never need to download or install any environments manually (e.g. you won't need to install Singularity or docker are the best way to deploy the pipeline - we only use conda as a backup. Is it possible you could get support from your sysadmins to work with singularity? |
Thank you so much for your help still! I will try to get them to install singularity. Best wishes |
I had an idea to create a big conda environment containing every dependency, but it should only be tried as a last resort: Please let me know if this approach works for you 😅 |
Thank you for your suggestion, I read shortly into that discussion and it should be possible to make it work, since I'm also working with the AllofUs cloud environment. Before I try that though, I was sent this page by the support team of AoU: https://support.researchallofus.org/hc/en-us/articles/21179878475028-Using-Docker-Images-on-the-Workbench And there's this short paragraph about using a docker image with Nextflow, would there be a way to adapt it to pgsc calc? Thank you again! |
@pecko-g could you try the conda profile with the latest release please. Sorry for the delay! 😄 https://pgsc-calc.readthedocs.io/en/latest/how-to/change_version.html |
The test profile works now! Thank you so much! 👏🏼 |
Description of the bug
Hi again,
I'm having trouble running the test profile of the pgsc calc in a new environment. When I run the test command, I get the error line "Module path must start with / or ./ prefix -- Offending module: plugin/nf-validation".
I had a look around some folders and couldn't find any "nf-validation" file/folder and I am unsure which config files I could correct.
I also just read that nf-validation is deprecated. I'm running nextflow version 22.04.5, could that be the problem? Unfortunately I don't have permission to update Nextflow on my own, so could there be a way around?
Thank you in advance.
Best wishes
Command used and terminal output
Relevant files
No response
System information
Nextflow version 22.04.5
The text was updated successfully, but these errors were encountered: