Sofia Stamouli
07/30/2026, 1:20 PMCanceling since a higher priority waiting request for Run nf-test-759 exists . Any ideas why is happening?Chris Wyatt
07/30/2026, 2:58 PMrazmia.sabahat
07/30/2026, 4:22 PMPatricie Skaláková
08/03/2026, 10:16 AMNick Waters
08/03/2026, 2:01 PMLouis Le Nézet
08/05/2026, 5:04 PM> ERROR conda.core.link:_execute(1014): An error occurred while installing package 'bioconda::spades-3.15.5-h95f258a_1'.
> Rolling back transaction:
> LinkError: post-link script failed for package bioconda::spades-3.15.5-h95f258a_1
> location of failed script: /home/runner/work/modules/modules/.nf-test/tests/769e57f0e7d8bc77bee19f97fef1c9d9/work/conda/env-27f8de4e77d219b103e2d1302f904167/bin/.spades-post-link.sh
> ==> script messages <==
> <None>
> ==> script output <==
> stdout:
> stderr: /home/runner/work/modules/modules/.nf-test/tests/769e57f0e7d8bc77bee19f97fef1c9d9/work/conda/env-27f8de4e77d219b103e2d1302f904167/etc/conda/deactivate.d/deactivate-gxx_linux-64.sh: line 68: CONDA_BACKUP_CXX: unbound variable
I've tried to specify additional libraries to match the singularity container, but I always came back to this error.
Does anybody know how to solve this ?
github.com/nf-core/modules/pull/12577Evangelos Karatzas
08/06/2026, 2:10 PM> Command error:
> WARNING: DEPRECATED USAGE: Forwarding SINGULARITYENV_NXF_TASK_WORKDIR as environment variable will not be supported in the future, use APPTAINERENV_NXF_TASK_WORKDIR instead
> WARNING: DEPRECATED USAGE: Forwarding SINGULARITYENV_NXF_DEBUG as environment variable will not be supported in the future, use APPTAINERENV_NXF_DEBUG instead
> ERROR : Failed to create container process: Operation not permittedNiklas Schandry
08/06/2026, 2:16 PMVikesh Ajith
08/07/2026, 4:00 AMmodules/nf-core/vuegen/.conda-lock/linux_amd64-bd-9eebdec0448f6563_1.txt
I'm able to get all the other information from:
seqera.io/containers
For reference, here is my container. There is a conda lockfile block there but it is a format that I don't really recognise and doesn't seem to match other modules with the lockfileSunil
08/07/2026, 9:06 PMprocess {
withName: 'BOWTIE2_ALIGN' {
ext.args = {
[
meta.read_group ? "--rg-id ${meta.id} --rg SM:${meta.id - ~/_T\\d+$/} --rg PL:ILLUMINA --rg LB:${meta.id} --rg PU:1" : '',
params.seq_center ? "--rg CN:${params.seq_center}" : '',
'-X 1000'
].join(' ').trim()
}
}
withName: 'BAMTOOLS_FILTER' {
ext.args = {
[
meta.single_end ? '-F 0x004' : '-F 0x004 -F 0x0008 -f 0x001',
params.keep_dups ? '' : '-F 0x0400',
params.keep_multi_map ? '' : '-q 30'
].join(' ').trim()
}
}eleni.afentaki
08/07/2026, 9:34 PMAlexandra Mancheno-Ferris
08/10/2026, 9:31 AMAra
08/10/2026, 12:07 PMnivethithaj59
08/15/2026, 9:56 AMfast basecalls only, no POD5.
• 600 Mb total → ~15× if it's a 40 Mb genome
• read N50 1,468 bp, median 1,219
• mean Q11.2, only 3.9% of reads above Q15
My conclusion: this can't produce a usable genome assembly, and the N50 alone is disqualifying — nothing spans an LTR element or an rDNA unit, so the repeat structure is unresolvable regardless of assembler or coverage.
Can anyone help me up here? Because previously the same issue happened and they did the re-sequencing and sent me up this data, which ultimately fails the QC requirement for the fungal assemby again.
Any suggestion or guidance would be helpful for me. Thanks in advanceJaime Zolik
08/19/2026, 1:09 PMWorkflow execution completed unsuccessfully!
The exit status of the task that caused the workflow execution to fail was: null.
The full error message was:
Error executing process > 'NFCORE_MAG:MAG:ANCIENT_DNA_ASSEMBLY_VALIDATION:PYDAMAGE_ANALYZE (SPAdes-22ds)'
Caused by:
process hasn't exited
Here is my code:
nextflow pull nf-core/mag
nextflow run nf-core/mag -r 5.5.0 \
-c custom.config \
-profile singularity \
--input /projects/standard/mnievesc/zolik006/01_projects/01_PIALQ/02_analysis/03_Metagenomics/01_analysis/04_Denovo/sam$
--clip_tool adapterremoval \
--host_fasta /projects/standard/mnievesc/shared/ref_seqs/human_g1k_v37.fasta \
--host_fasta_bowtie2index /projects/standard/mnievesc/shared/ref_seqs \
--spades_fix_cpus 32 \
--megahit_fix_cpu_1 \
--reads_minlength 30 \
--binning_map_mode own \
--min_contig_size 500 \
--save_assembly_mapped_reads \
--exclude_unbins_from_postbinning \
--skip_prokka \
--run_checkm \
--run_busco \
--checkm_db /projects/standard/mnievesc/zolik006/02_refseqs/09_metaWARP/CheckM_DB \
--refine_bins_dastool \
--refine_bins_dastool_threshold 0.3 \
--postbinning_input refined_bins_only \
--run_gunc \
--gunc_db /projects/standard/mnievesc/zolik006/02_refseqs/11_gunc/gunc_db_progenomes2.1.dmnd \
--gtdb_db /projects/standard/mnievesc/zolik006/gtdbtk/share/gtdbtk-2.6.1/db \
--ancient_dna \
--outdir /projects/standard/mnievesc/zolik006/01_projects/01_PIALQ/02_analysis/03_Metagenomics/01_analysis/04_Denovo/
And my custom.config:
process {
withName: GTDBTK_CLASSIFYWF {
cpus = 32
memory = 256.GB
}
withName: CHECKM_QC {
cpus = 32
memory = 256.GB
}
withName: PYDAMAGE_ANALYZE {
cpus = 32
memory = 256.GB
}
}
When I look at the .command.log in the work-directory I can see that it completed analyzing all of the sequences.
I am only putting in one ancient DNA sequencing file (22ds) that has about 18 million reads. I do not know what is causing it to get stuck on phydamage and would appreciate any advice on what I can do to fix this.Luis Heinzlmeier
08/20/2026, 8:19 AMnf-core pipelines sync \
--dir /Users/luisheinzlmeier/Desktop/Repos/hadge \
--from-branch dev \
--pull-request \
--username LuisHeinzlmeier \
--github-repository <https://github.com/nf-core/hadge.git>
,--./,-.
___ __ __ __ ___ /,-._.--~\
|\ | |__ __ / ` / \ |__) |__ } {
| \| | \__, \__/ | \ |___ \`-._,-`-,
`._,._,'
nf-core/tools version 4.1.0 - <https://nf-co.re>
WARNING Could not find GitHub authentication token. Some API requests may fail.
WARNING Could not find GitHub authentication token. Some API requests may fail.
INFO Pipeline directory: /Users/luisheinzlmeier/Desktop/Repos/hadge
INFO Using branch 'dev' to fetch workflow variables
INFO Will attempt to automatically create a pull request
INFO Original pipeline repository branch is 'dev'
INFO Deleting tracked files in 'TEMPLATE' branch
INFO Making a new template pipeline using pipeline variables
INFO Using found ORCID for Fabiola Curion. Please double-check: <https://orcid.org/0000-0003-2502-8803>
INFO Saving metadata file to '/Users/luisheinzlmeier/Desktop/Repos/hadge'
INFO Generated container configs for the pipeline.
INFO Committed changes to 'TEMPLATE' branch
INFO Pushing TEMPLATE branch to remote: 'hadge'
INFO Checking out original branch: 'dev'
ERROR Could not push TEMPLATE branch:
Cmd('git') failed due to: exit code(1)
cmdline: git push
stderr: 'remote: error: GH013: Repository rule violations found for refs/heads/TEMPLATE.
remote: Review all repository rules at <https://github.com/nf-core/hadge/rules?ref=refs%2Fheads%2FTEMPLATE>
remote:
remote: - Cannot update this protected ref.
remote:
To <https://github.com/nf-core/hadge.git>
! TEMPLATE -> TEMPLATE (push declined due to repository rule violations)
error: failed to push some refs to '<https://github.com/nf-core/hadge.git''>
Thank you for your help!Slackbot
08/20/2026, 11:13 AMaydinalimert
08/20/2026, 7:08 PMSINRASU ALAGUDURAI
08/31/2026, 5:16 AMaws.batch.platformType setting is global for the entire workflow (ec2 or fargate).
• There does not appear to be a per-process platformType configuration.
• As a result, all dynamically created job definitions inherit the same platform capability (EC2 or Fargate).
My question is:
Is it possible to run a single Nextflow workflow across both Fargate and EC2 compute environments without using pre-registered AWS Batch job definitions (job-definition://) ?
For example:
• Lightweight processes run on a Fargate-backed queue.
• High-resource processes (e.g., requiring 48 vCPUs) run on an EC2-backed queue.
• Nextflow manages job-definition creation automatically.
• No manually created AWS Batch job definitions are used.
From what I've been able to determine, this is not possible, because the dynamically registered job definitions are created with a single platform capability based on the global aws.batch.platformType setting, and AWS Batch queues require the job definition's platform capability to match the underlying compute environment.
Can anyone confirm whether this understanding is correct, or if there is another supported approach for mixing EC2 and Fargate within the same workflow run without manually managing job definitions?
Thanks!Mahesh Binzer-Panchal
09/03/2026, 1:38 PMJasmin Frangenberg
09/08/2026, 6:34 PMERROR Could not parse Nextflow config for
'/home/runner/work/funcscan/funcscan'. Possibly because of a Nextflow
version mismatch?
Command 'nextflow config -o json /home/runner/work/funcscan/funcscan'
failed with exit code 1
Downloading plugin nf-schema@2.7.2
ERROR ~ No such variable: meta
Error: Process completed with exit code 1.Kurayi
09/11/2026, 8:02 AMThiseas C. Lamnidis
09/11/2026, 5:10 PM.nf-test.config like so, but that doesn’t seem to do it.
// ignore tests coming from the nf-core/modules repo
ignore = [
'modules/nf-core/**/tests/*',
'subworkflows/nf-core/**/tests/*',
'tests/test_full.nf.test*', // Ignore test_full in CI.
]
Is there another spot I can tweak this at?Daniel Lundin
09/14/2026, 2:24 PMThiseas C. Lamnidis
09/16/2026, 12:05 PMoutput:
my_data_package/
file1
file2
So that the channel output is not simply:
channel1 = [file1]
channel2 = [file2]
but
channel1 = [ [id:"my_data_package"], file1]
channel2 = [ [id:"my_data_package"], file2]Niklas Schandry
09/17/2026, 7:34 AMbwamem2_index module behaviour, it requests memory, based on memory { 280.MB * _Math_.ceil(fasta.size() / 10000000) * task.attempt } . However, on AWS it OOMs even on attempt 3. The log states:
ref seq len = 315317090 which I assume is the length of the sequence. By my math (315317090*280/10000000), this should request 8.828 MB * task.attempt, but according to the AWS metrics for this job it requested 3.3 GB for the third (1.1GB per attempt). This also was not an issue before, so I am a bit confused whats going wrong.Andrea Bagnacani
09/17/2026, 1:27 PMv0.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?Niklas Schandry
09/18/2026, 8:11 AMgiulia.roeth
09/18/2026, 4:14 PMNick Waters
09/21/2026, 12:39 PM! [remote rejected] 1.0.0 -> 1.0.0 (push declined due to repository rule violations)
and I can't do it via the web
Tag could not be created. Pre-receive hooks failed. repository rule violations found
Cannot create ref due to creations being restricted.
`