-
Notifications
You must be signed in to change notification settings - Fork 94
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
multiprocessing.pool.MaybeEncodingError building reference for fusion-report #402
Comments
I can reproduce. It is due to an extra layer of security from the ccsm.uth.edu website that was just added. Can you please try again? I overwrote the container by mistake, so you can actually just use the same branch. I will sort the container situation in the next few days |
Thanks for your help. I still have the same error after cleaning my Nextflow and Singularity caches and resubmitting with the same command, but looking at Docker Hub I suspect you started fixing the containers, should I try later ? |
Yes, was just going to write that the container situation should be fixed and I just merged the PR to link rnafusion to the right fusionreport container. So you can try dev again! |
Different error this time (still the same command, after cleaning caches) :
At some point it mentioned it pulled the "p4" image as expected. |
I have to highlight I'm using a proxy (passed through |
This one I cannot reproduce, and most likely is due to the proxy indeed. You could download locally (the download should be lightweight) and copy to HPC after as detailed in Line 69 in 62f78be
|
I managed to build it locally following the documentation you provided, thanks a lot for your help ! |
Description of the bug
Following issue #397 I'm still facing problems with fusion-report when building reference from the
dev
reference (currently6dfedc2213c806e99ced690fe0fc2e92d6f01102
).Command used and terminal output
./nextflow-23.09.1-edge-all -c custom.conf run nf-core/rnafusion -r dev -profile singularity --outdir build --all --build_references --cosmic_username "REDACTED" --cosmic_passwd "REDACTED"
Relevant files
custom.conf.zip
System information
dev
The text was updated successfully, but these errors were encountered: