Dear all, I created a private nextflow repository for my organization's modules/subworkflows using the copier template. This has worked smoothly in the last month. However, today it seems that

v0.0.6

(the latest version) of detect-nf-test-changes GitHub action cannot run, because it tries to fetch debian packages from a mirror location that is not available:

#8 3.101 E: Failed to fetch <http://deb.debian.org/debian-security/pool/updates/main/p/perl/perl-base_5.32.1-4%2bdeb11u5_amd64.deb>  404  Not Found [IP: 151.101.74.132 80]
...
ERROR: failed to build: failed to solve: process "/bin/sh -c apt-get update     && apt-get install -y git     && pip install --no-cache-dir --upgrade pip     && pip install -r requirements.txt" did not complete successfully: exit code: 100

Do you know how to solve this issue?

That looks like a temporary glitch, if you rerun the action it's likely to succeed.

Thank you, pontus. I'll try it

I can open that link from my computer

Ok, the name deb.debian.org will resolve to a number of mirrors and at least one of them is lagging, it seems (might also depend on where your runner happens to be placed), but there doesn't seem to be anything wrong with what it's doing.

The copier template is close to 12 months behind

nf-core/modules

, it’s due an update. With an update though, it’d move away from

nf-test-changes

since there’s a different implementation in nf-core/modules now

Dear all, I can confirm that it is not a glitch. Re-running the GitHub action consistently fails with the same error. However, I just realized that I might have copied an incomplete error log:

nf-test-changes

had a similar (and solved) issue 2 weeks ago; there, the error does not involve

perl

, but similarly the fact that the image cannot ultimately be built. The fix is not yet part of a release. Since my repo relies on the latest

nf-test-changes v0.0.6

, I locally edited my configuration as follows:

- name: List nf-test files
        id: list
        #uses: adamrtalbot/detect-nf-test-changes@de3c3c8e113031b4f15a3c1104b5f135e8346997 # v0.0.6
        uses: adamrtalbot/detect-nf-test-changes@accef9459c66baa65dbca647615f088b98eefa9c # Fixes v0.0.6
...

This solves the issue