nextflow-io / nextflow-io/nextflow
-stub before another option (not directly before the pipeline arg) resolves wrong pipeline (nextflow-io/true)
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
Bug report
Expected behavior and actual behavior
-stub/-stub-run, when immediately followed by another option (rather than
directly by the pipeline argument or the end of the command), causes Nextflow
to resolve the wrong pipeline: instead of pulling the given URL/name, it pulls
nextflow-io/true and fails with a "Remote resource not found" error.
Likely related to #3437 ("-stub-run as first option causes
failure"), filed in 2022 against 22.10.3 with the identical nextflow-io/true
symptom, which was auto-closed by stale-bot.
Steps to reproduce the problem
$ nextflow run -ansi-log false -stub -profile docker https://github.com/nf-core/fetchngs -r 0ae5518 -latest
vs. the same command with only -stub moved to the end:
$ nextflow run -ansi-log false -profile docker https://github.com/nf-core/fetchngs -r 0ae5518 -latest -stub
Also reproduces with a semver tag instead of a commit SHA (-r 1.12.0), with
-stub true (giving -stub an explicit value), and with the
short org/repo pipeline form, but not when -stub is immediately
followed directly by the pipeline argument itself.
Program output
Failing invocation:
Pulling nextflow-io/true:0ae5518 ...
WARN: Cannot read project manifest -- Cause: Remote resource not found: https://api.github.com/repos/nextflow-io/true/contents/nextflow.config?ref=0ae5518
Remote resource not found: https://api.github.com/repos/nextflow-io/true/contents/main.nf?ref=0ae5518
Same command with -stub moved after the pipeline argument:
Pulling nf-core/fetchngs:0ae5518 ...
Environment
- Nextflow version:
26.04.6.12646 - Java version:
openjdk 17.0.20 2026-07-21 - Operating system: Debian GNU/Linux 12 (bookworm) — also confirmed on macOS
with the same Nextflow version
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failing and working nextflow run commands shown in the issue, then trace the command-line option parsing for -stub and pipeline arguments. Done means options before the pipeline no longer cause resolution to nextflow-io/true, while the shown URL, tag, commit, and short pipeline forms still resolve correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100