-
Notifications
You must be signed in to change notification settings - Fork 191
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
download pipelines fails with some seqera containers #3285
Comments
Thanks a lot for this in depth investigation. I need to explore this further, but if it is indeed an issue with two processes competing for the same cached blob, the download should work, if you additionally provide the argument |
That works! |
Yes, I tested on Gitpod as well and also found the bug. The problem is, that I had to ream the If there are multiple modules in the pipeline that use the same container (like in fastquorum), the identical container URIs will be extracted and in the case of Seqera containers not deduplicated. Hence, we get the race condition in the cache, that you observed. In terms of tools, the fix is very simple. In But I would also like to have a test for the future, so the PR is a bit more comprehensive than that. I am working on it. |
Fix is on its way: #3293 |
Description of the bug
Error encountered when installing dev branch of fastquourum with latest nf-core/tools build.
@MatthiasZepper helped with a little digging.
I did a little additional digging on a branch and commented out one progress logging line that seemed to be triggering the key error and added a few additional debug statements.
This generates a new error:
In my debug statements it almost looks like this could be a repeated action error. There are two processes that share use this image (not sure if that could be relevant).
In my debug statements I can see that file is made and opened.
It looks like the singularity and docker images are found.
Extra weirdness. I think the final expected file exists and is the correct size, 825028608 == 825028608.
Command used and terminal output
System information
Nextflow version: 24.10.1
Hardware: AWS t2-micro
Executor: NA
OS: Amazon Linux
nf-core/tools version: dev
Python version: 3.12
The text was updated successfully, but these errors were encountered: