OCI team has just released

nf-rest

plugin which works with

oci

, please feel free to test and provide feedback.

Hi, I'm just testing a plugin from the template.

gradlew assemble

and

test

are ok but I cannot find the proper way to launch a workflow with the plugin:

export NXF_PLUGINS_DIR=/home/me/PLUGINS_DIR && \
export NXF_PLUGINS_DEFAULT=false && \
export NXF_PLUGINS_DEV=/home/me/myplugin && \
export NXF_PLUGINS_MODE=dev && \
nextflow run -resume <http://main.nf|main.nf> --samplesheet jeter.list
N E X T F L O W  ~  version 25.10.2
WARN: It appears you have never run this project before -- Option `-resume` is ignored
ERROR ~ Cannot invoke "org.pf4j.Plugin.start()" because the return value of "org.pf4j.PluginWrapper.getPlugin()" is null

but the classes are here:

/home/me/PLUGINS_DIR/
/home/me/PLUGINS_DIR/myplugin-0.1.0
/home/me/PLUGINS_DIR/myplugin-0.1.0/classes
/home/me/PLUGINS_DIR/myplugin-0.1.0/classes/lindenb
/home/me/PLUGINS_DIR/myplugin-0.1.0/classes/lindenb/plugin

the project is here:

/home/me/myplugin/settings.gradle

in the nexflow.log there is a classnotfound exception:

Dec-10 13:25:51.130 [main] ERROR org.pf4j.DefaultPluginFactory - lindenb.plugin.RdfgraphPlugin
java.lang.ClassNotFoundException: lindenb.plugin.MypluginPlugin
        at org.pf4j.PluginClassLoader.loadClass(PluginClassLoader.java:169)
        at org.pf4j.DefaultPluginFactory.create(DefaultPluginFactory.java:44)
        at org.pf4j.PluginWrapper.getPlugin(PluginWrapper.java:94)
        at org.pf4j.AbstractPluginManager.startPlugin(AbstractPluginManager.java:441)
        at nextflow.plugin.PluginUpdater.prepareAndStart(PluginUpdater.groovy:181)
        at nextflow.plugin.PluginsFacade.start(PluginsFacade.groovy:401)
        at nextflow.plugin.PluginsFacade.load(PluginsFacade.groovy:291)
        at nextflow.plugin.Plugins.load(Plugins.groovy:50)
        at nextflow.cli.CmdRun.run(CmdRun.groovy:364)
        at nextflow.cli.Launcher.run(Launcher.groovy:515)
        at nextflow.cli.Launcher.main(Launcher.groovy:675)

( I changed the names) What Am i doing wrong ?

Hi Again, In *Observer.groovy , how can I find the names of the files that were produced by a cached/completed process ? So far, I only found handler.task.getOutputFilesNames() ( returns something like '*.txt' ) or handler.task.getOutputEvals() (empty map )

Hello everyone, I’m trying to compile a Nextflow plugin. The compilation works without any errors on my side. However, when I try to use the plugin on a computing cluster, I get the following error:

java.lang.UnsupportedClassVersionError: nextflow/executor/slurm_no_memory/SlurmNoMemoryPlugin has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognises class file versions up to 55.0

To fix this, I attempted to compile the plugin using Java 11. The build completes successfully, but I still get the same error on the cluster. I checked the compiled classes with this command:

find build/classes/groovy/main/ -name '*.class' -exec javap -verbose {} 2>/dev/null \; | grep 'major'

and the output still shows

major version: 61

instead of 55. I also tried building the plugin inside a Singularity container, but the problem remains. Below is my

build.gradle

. If anyone has suggestions on how to force Gradle/Groovy to compile the plugin with Java 11 bytecode, I would really appreciate your help. Thanks in advance!

I get the following error message when trying to claim a plugin in the registry:

Description validation failed: AI validation service unavailable: {"error":{"message":"The free Devstral 2 2512 period has ended. To continue using this model, please migrate to the paid slug: mistralai/devstral-2512","code":404},"user_id":"org_37DPlhKI977Qlk0QHp6DXMb3EkV"}

Question from someone who doesn't really understand the world of Java packages, can we import a nextflow plugin into another piece of Java/Groovy software?

qq: I maintain nf-fgbio; what's the best way to adapt a plugin that uses the legacy plugin index to use the new plugin registry? Any gotchas?

Hey everyone! 👋 Apologies if this isn't quite the right channel for this, but we just published a new plugin: nf-itdepends 🎉 🔗 https://registry.nextflow.io/plugins/nf-itdepends@0.1.0 G https://github.com/fulcrumgenomics/nf-itdepends If you've been missing the ability to use Maven dependencies in your custom Groovy

lib/

code since Apache Ivy was removed in Nextflow 24.04.7-edge, this plugin brings it back. Just add it to your config and you can use

@Grab

to pull in any dependency you need, just like before. Setup is just adding the plugin to your `nextflow.config`:

plugins {
    id 'nf-itdepends@0.1.0'
}

I stumbled across this issue while debugging cloud cache issues and added a comment with my solution. I wonder if any maintainers of

nf-google

had thoughts: https://github.com/nextflow-io/nextflow/discussions/4876#discussioncomment-15799679

Hey everyone! Apologies if this isn't quite the right channel for this, but we just published a new plugin: nf-slurm-no-memory 🎉 🔗 https://github.com/bioinfo-pf-curie/nf-slurm-no-memory 🔗 https://registry.nextflow.io/plugins/nf-slurm-no-memory@1.0.0 If you're working on HPC clusters where memory limits cannot be explicitly set (i.e. no

--mem

or

--mem-per-cpu

), this plugin may be exactly what you've been missing. Many clusters enforce a fixed memory-per-CPU ratio, and this plugin restores the ability for Nextflow to adapt automatically by computing the optimal CPU count for each process. Just add it to your config, set the executor to

slurm_no_memory

, and Nextflow will dynamically calculate the required CPUs based on the process memory request and the cluster’s memory-per-CPU policy (default: 4 GB/CPU).

plugins {
    id 'nf-slurm-no-memory@1.0.0'
}

Hey everyone! We've just open-sourced a new plugin: nf-cgroup-metrics https://github.com/watchmaker-genomics/nf-cgroup-metrics If you're right-sizing your processes, you need accurate memory metrics. Nextflow's default memory tracking is unreliable in containerized environments, overreporting for some tools and underreporting for others. This makes it difficult to right-size appropriately. This plugin replaces Nextflow's default memory tracking with cgroup metrics. These are the same metrics your container runtime uses to enforce memory limits and trigger OOM kills. Also available on the Nextflow plugin registry: https://registry.nextflow.io/plugins/nf-cgroup-metrics

I'm working on a plugin for easier / more readable ways to grep tool versions for MultiQC: • https://github.com/fulcrumgenomics/nf-versions Not in the plugin registry yet, but I'm hoping something like this gains traction. PRs welcome for community tools that don't exist yet. I also haven't supported version groups yet, but that shouldn't be too hard.

I had a thought yesterday. It’s a minor addition, but I think it’d be useful: adding a check at the end of the pipeline to verify if the Nextflow plugins are up to date what do you think?

Hi all, I have a small question/scenario re: core plugin versions Is the drift between https://registry.nextflow.io/ and https://github.com/nextflow-io/plugins/blob/main/plugins.json intended? Ie., v25 default nf-google versions are in the new registry but not the GH plugin index repo/nor the nf-google dedicated GH release page

We’re having some issues using

nf-cloudcache

. We cant’ seem to get the resume functionality to work. submission script:

export NXF_VER=25.10.3
export NXF_JVM_ARGS="-Xms2048m -Xmx8192m"
export NXF_CLOUDCACHE_PATH="<s3://cmgg-cloudcache/cache>"

nextflow run nf-cmgg/smallvariants -r dev \
    --input /projects/exome/smallvariants/NVQX_307/germline_samplesheet.csv \
    --outdir . \
    --multiqc_title NVQX_307 \
    --ped /projects/exome/smallvariants/NVQX_307/Probands_NVQX_307.ped \
    -plugins nf-nomad@99.99.99 \
    -resume \
    -ansi-log false

Hey all! Just opened a request to add a new plugin

nf-logsaver

to the Nextflow plugin directory. It will automatically move the '.command.err', '.command.sh' and '.command.out' for each step in a pipeline into a new log directory. It will also rename them with the step name and the short hash of that iteration to make it easier to a) find the log files that you need to debug a particular step and b) make sure that they are safely out of the work directory (in the case that you need/want to hold on to these) without needing to modify the underlying pipeline. Would love any feedback or suggestions you have, code currently lives here: https://github.com/miraep8/nf-logsaver

Can somebody perhaps explain to me why Nextflow 25.10 is so terribly homesick? We have an offline HPC cluster, so I need to store the plugins locally. I have configured

NXF_PLUGINS_DIR

and to me it also seems that it it indeed recognizes the correct path

/vulpes/proj/ngis/ngi2016004/nobackup/nf-core-tower/tower-nxf-home/.nextflow/plugins

I have also pinned the plugin versions in the config:

plugins {
    id 'nf-co2footprint@1.2.0'
    id 'nf-tower@1.23.0'
    id 'nf-schema@2.6.1'
}

Yet, it seems that Nextflow desperately wants to reach home for reasons that I do not understand:

Mar-27 19:45:08.626 [main] DEBUG nextflow.plugin.PluginsFacade - Setting up plugin manager > mode=prod; embedded=false; plugins-dir=/vulpes/proj/ngis/ngi2016004/nobackup/nf-core-tower/tower-nxf-home/.nextflow/plugins; core-plugins: nf-amazon@3.4.1,nf-azure@1.20.2,nf-cloudcache@0.5.0,nf-codecommit@0.5.0,nf-console@1.3.0,nf-google@1.23.3,nf-k8s@1.2.2,nf-tower@1.17.1,nf-wave@1.16.1
Mar-27 19:45:08.658 [main] INFO  o.pf4j.DefaultPluginStatusProvider - Enabled plugins: []
Mar-27 19:45:08.658 [main] INFO  o.pf4j.DefaultPluginStatusProvider - Disabled plugins: []
Mar-27 19:45:08.659 [main] INFO  org.pf4j.DefaultPluginManager - PF4J version 3.12.0 in 'deployment' mode
Mar-27 19:45:08.668 [main] DEBUG nextflow.util.RetryConfig - Missing nextflow session - using default retry config
Mar-27 19:45:08.731 [main] INFO  org.pf4j.AbstractPluginManager - No plugins
Mar-27 19:45:08.732 [main] DEBUG nextflow.plugin.PluginsFacade - Plugins declared=[nf-co2footprint@1.2.0, nf-tower@1.23.0, nf-schema@2.6.1]
Mar-27 19:45:08.733 [main] DEBUG nextflow.plugin.PluginsFacade - Plugins default=[nf-tower@1.17.1]
Mar-27 19:45:08.734 [main] DEBUG nextflow.plugin.PluginsFacade - Plugins resolved requirement=[nf-co2footprint@1.2.0, nf-tower@1.23.0, nf-schema@2.6.1]
Mar-27 19:49:29.838 [main] DEBUG io.seqera.http.HxClient - HTTP request retry attempt 1: null
Mar-27 19:53:52.421 [main] DEBUG io.seqera.http.HxClient - HTTP request retry attempt 2: null
Mar-27 19:58:15.255 [main] DEBUG io.seqera.http.HxClient - HTTP request retry attempt 3: null
Mar-27 20:02:39.365 [main] DEBUG io.seqera.http.HxClient - HTTP request retry attempt 4: null
Mar-27 20:07:02.116 [main] DEBUG io.seqera.http.HxClient - HTTP request retry attempt 5: null
Mar-27 20:07:02.121 [main] ERROR nextflow.cli.Launcher - Conversion = '4'
java.util.UnknownFormatConversionException: Conversion = '4'
        at java.base/java.util.Formatter.parse(Formatter.java:2852)
        at java.base/java.util.Formatter.format(Formatter.java:2774)
        at java.base/java.util.Formatter.format(Formatter.java:2728)
        at java.base/java.lang.String.format(String.java:4386)
        at org.pf4j.util.StringUtils.format(StringUtils.java:39)
        at org.pf4j.PluginRuntimeException.<init>(PluginRuntimeException.java:41)
        at nextflow.plugin.HttpPluginRepository.fetchMetadata0(HttpPluginRepository.groovy:140)
        at nextflow.plugin.HttpPluginRepository.fetchMetadata(HttpPluginRepository.groovy:123)
        at nextflow.plugin.HttpPluginRepository.prefetch(HttpPluginRepository.groovy:70)
        at nextflow.plugin.PluginUpdater.prefetchMetadata(PluginUpdater.groovy:154)
        at nextflow.plugin.PluginsFacade.start(PluginsFacade.groovy:398)
        at nextflow.plugin.PluginsFacade.load(PluginsFacade.groovy:291)
        at nextflow.plugin.Plugins.load(Plugins.groovy:50)
        at nextflow.cli.CmdRun.run(CmdRun.groovy:363)
        at nextflow.cli.Launcher.run(Launcher.groovy:515)
        at nextflow.cli.Launcher.main(Launcher.groovy:675)

because all those plugins are available in the

NXF_PLUGINS_DIR

.

ls /vulpes/proj/ngis/ngi2016004/nobackup/nf-core-tower/tower-nxf-home/.nextflow/plugins
nf-amazon-1.16.2       nf-co2footprint-1.0.0-beta   nf-cws-1.0.2             nf-google-1.8.3     nf-prov-1.2.3    nf-schema-2.4.0        nf-tower-1.11.4  nf-tower-1.5.3       nf-validation-1.1.4  nf-weblog-1.1.2
nf-amazon-1.3.4        nf-co2footprint-1.0.0-beta1  nf-cws-1.0.3             nf-gpt-0.4.0        nf-prov-1.2.4    nf-schema-2.4.1        nf-tower-1.12.0  nf-tower-1.5.4       nf-wave-0.13.0       nf-wr-1.2.0-rc.2
nf-amazon-2.1.3        nf-co2footprint-1.0.0-rc     nf-cws-1.0.5             nf-hello-0.1.0      nf-prov-1.3.0    nf-schema-2.4.2        nf-tower-1.13.0  nf-tower-1.5.6       nf-wave-0.8.4        xpack-amzn-1.2.1
nf-amazon-2.1.4        nf-co2footprint-1.0.0-rc.1   nf-dotenv-1.0.0          nf-hello-0.2.0      nf-prov-1.4.0    nf-schema-2.5.0        nf-tower-1.14.0  nf-tower-1.6.2       nf-wave-1.0.0        xpack-amzn-1.3.1
nf-amazon-2.5.2        nf-co2footprint-1.0.0-rc.2   nf-ffq-0.2.0             nf-hello-0.3.0      nf-prov-1.5.0    nf-schema-2.5.1        nf-tower-1.17.2  nf-tower-1.6.3       nf-wave-1.10.0       xpack-amzn-1.6.0
nf-amazon-2.9.1        nf-co2footprint-1.0.0-rc.3   nf-float-0.3.1           nf-hello-0.5.0      nf-prov-1.6.0    nf-schema-2.6.0        nf-tower-1.17.3  nf-tower-1.9.1       nf-wave-1.11.0       xpack-google-1.0.0
nf-amazon-3.4.1        nf-co2footprint-1.1.0        nf-float-0.4.6           nf-ignite-1.2.3     nf-prov-1.7.0    nf-schema-2.6.1        nf-tower-1.17.4  nf-tower-1.9.3       nf-wave-1.11.1       yellowdog-1.0.1
nf-azure-1.0.1         nf-co2footprint-1.2.0        nf-ga4gh-1.0.5           nf-iridanext-0.3.0  nf-quilt-0.4.5   nf-snowflake-0.6.0     nf-tower-1.17.5  nf-validation-0.3.1  nf-wave-1.12.0
nf-azure-1.10.2        nf-codecommit-0.1.4          nf-ga4gh-1.1.0           nf-jarvice-0.7.0    nf-quilt-0.9.1   nf-sqldb-0.5.0         nf-tower-1.18.0  nf-validation-0.3.2  nf-wave-1.12.1
nf-azure-1.3.2         nf-codecommit-0.1.5          nf-ga4gh-1.3.0           nf-nomad-0.3.1      nf-schema-2.0.0  nf-synapse-1.0.0       nf-tower-1.19.0  nf-validation-0.3.3  nf-wave-1.13.0
nf-azure-1.6.0         nf-codecommit-0.2.2          nf-google-1.13.2-patch1  nf-parquet-0.2.0    nf-schema-2.0.1  nf-tencentcloud-2.0.1  nf-tower-1.20.0  nf-validation-1.0.0  nf-wave-1.14.0
nf-boost-0.4.0         nf-console-1.0.3             nf-google-1.15.2         nf-pgcache-1.0.0    nf-schema-2.1.1  nf-tower-1.11.0        nf-tower-1.21.0  nf-validation-1.1.0  nf-wave-1.14.1
nf-cloudcache-0.2.0    nf-console-1.0.5             nf-google-1.7.3          nf-prov-1.1.0       nf-schema-2.2.0  nf-tower-1.11.1        nf-tower-1.22.0  nf-validation-1.1.1  nf-wave-1.16.1
nf-cloudcache-0.4.2    nf-console-1.0.6             nf-google-1.7.3-patch1   nf-prov-1.2.1       nf-schema-2.2.1  nf-tower-1.11.2        nf-tower-1.23.0  nf-validation-1.1.2  nf-wave-1.7.3
nf-co2footprint-1.0.0  nf-console-1.1.4             nf-google-1.8.2          nf-prov-1.2.2       nf-schema-2.3.0  nf-tower-1.11.3        nf-tower-1.5.12  nf-validation-1.1.3  nf-weblog-1.1.0

What am I missing?

I have a Nextflow plugin review for inclusion in the registry but it's been a few weeks. How long can I expect that approve/deny process to take?

Hi, I found an error regarding the versioning of plugins when attempting to call

nextflow plugin <name>@<version>:<command>

, but received no responses thus far on the Issue: https://github.com/nextflow-io/nextflow/issues/7110 and PR https://github.com/nextflow-io/nextflow/pull/7113. Some feedback would be welcome.

I'm using an aws sso pattern to authenticate my terminal to assume the role i need to access data on S3. This works fine on nextflow 25.10.4-dist which uses the nf-amazon plugin from the registry. However, nextflow 25.04.6-dist bundles nf-amazon@2.15.0 and will fail to find the credentials, "falling back on anonymous access" and failing with an S3 AccessDenied error. Since I still need to support nextflow releases as far back as 23.10.1, how should I proceed? Below is a redacted representation of my ~/.aws/config

[sso-session my-company]
sso_start_url = ...
sso_region = us-east-1
sso_registration_scopes = sso:account:access
[profile login-profile]
sso_session = my-company
sso_account_id = ...
sso_role_name = proxy-jump-role
[profile actual-role]
role_arn = ...
source_profile = login-profile

Hello! I draft a plugin for sending the log of a nextflow pipeline to an LLM (local or not) for explaining better the errors... it is called nf-llm-debugger https://github.com/biocorecrg/nf-llm-debugger

Good morning! I understand that each new plugin requires an approval... since you already approved the name space, what about considering some "institution" like trustworthy for their plugin (does it work with modules too?). This will make things easier

btw I have another plugin waiting for approval 🙂 nf-lims

Hello again and sorry to be doing lot of submission lately 🙂 But my IT decided to push on iRODs so I had to make a plugin to avoid too much manual work. the name is nf-irods but I can change to nf-crg-irods if is not too general.

[FIXED] I'm getting an error on plugin release today. I think from a slack search this might need fixing on the registry end

Error: INVALID_DESCRIPTION

    AI validation service unavailable: {"error":{"message":"User not found.","code":401}}

What's the proper way to do integration tests for a core plugin? I want to test some changes to nf-k8s on my infra but locally built nextflow keeps pulling down the latest nf-k8s rather than using the locally built version

Hallo everyone! Apologies if this isn't quite the right channel, but I just published a new plugin, nf-runinsights, for cross-run benchmarking of Nextflow pipelines. registry.nextflow.io/plugins/nf-runinsights github.com/QuietFlare/nf-runinsights Nextflow's built-in reports only describe a single run. This plugin remembers your runs and compares them. Every run writes its per-process metrics into a local history store (a shared directory or S3 works too, no server needed) and each new run gets checked against the older ones. It flags regressions and tries to name the likely cause, like queue wait vs actual execution, a container change, or plain input growth. It also spots over-provisioned resources and pipeline-wide slowdowns. It only observes, so it can't change or fail a run. There is also a small dashboard with no dependencies and an MCP server, so you can ask your AI assistant things like "why was last night's run slow?" Trying it is one config line

plugins { id 'nf-runinsights@0.1.0' }

So far I've only validated it on local runs of nf-core/sarek. If you run the same pipeline repeatedly on a cluster or in the cloud, I'd love to hear whether the findings hold up at that scale and what's missing. Thank you in Advance!

Sunday chill, nextflow plugin for TypeSafe Jev registry.nextflow.io/plugins/…

Like podcasts? Love plugins? Then this is for you!

Hello! Please can a registry admin transfer ownership of the

nf-synapse

plugin (registry.nextflow.io/plugins/nf-synapse) from me (adam.taylor@sagebase.org) to my colleague Aditi (aditi.gopalan@sagebase.org)? The Provider stays Sage Bionetworks. Aditi got "this plugin is already owned" when she tried to claim it. Thanks!