Harshil Patel

This is really weird. @mahesh-panchal any idea why having the closure would cause this problem?

Ahhh. So it's a scope issue The closure evaluates any variables in the local scope as priority? So we can either change the input value to something else or remove...

I would still be in favour of removing the closure if we don't need it for simplicity. Let's see what @mahesh-panchal thinks.

Yes, I saw the same thing: ``` Caused by: Failed to pull singularity image command: singularity pull --name containers.biocontainers.pro-s3-SingImgsRepo-imputeme-vv1.0.7_cv1-imputeme_vv1.0.7_cv1.img.img.pulling.1637839133887 https://containers.biocontainers.pro/s3/SingImgsRepo/imputeme/vv1.0.7_cv1/imputeme_vv1.0.7_cv1.img > /dev/null status : 143 message: INFO: Downloading network image...

We couldn't get it working consistently without the evaluation anyway so will leave things as they are and update later if required.

Hi @chbk! Can you try and re-run the pipeline by adding `-resume` to the command? I have seen this error before but it seems to sort itself out for some...

Sorry, this may actually be a bug. I was getting my wires crossed with another error. Would you mind sending my the full command and any custom configuration you used...

Hi @elffairy90 ! Did you manage to figure this out? Thanks!

Thanks for the detailed info and references @husaynahmed @houghtos. Having thought about this a little I think this is something that would be ideal to implement as a sub-workflow using...

For reference, just seen this GitHub Actions code [here](https://github.com/Golob-Minot/geneshot/blob/master/.github/workflows/release.yaml)