sanitizeOutput() drops all outputs of a process with only unnamed outputs
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 79/100
Research direction
Start by locating sanitizeOutput() and the tests covering output channel maps; the issue does not name their file paths. Reproduce the example with multiple unnamed outputs, then check the mixed named and unnamed case. Done means both unnamed outputs remain in the sanitized snapshot, including when named outputs are present, and the snapshot no longer matches an empty map.
Written by the indexing model from the issue text.
Description
sanitizeOutput() skips numeric channel keys whenever the channel map has more than one entry, assuming they duplicate named outputs. A process with several unnamed outputs only has numeric keys, so everything is dropped and the snapshot is an empty map that always matches.
process UNNAMED {
output:
path "a.txt"
path "b.txt"
script:
"""
echo a > a.txt
echo b > b.txt
"""
}
println process.out // [0:[.../a.txt], 1:[.../b.txt]]
println sanitizeOutput(process.out) // [:]
The same check also drops an unnamed output that sits next to named ones.
Reproduced on main (1.3.0) with Nextflow 26.10.0 and nf-test 0.9.5.
Possible fix: skip a numeric key only when its value is also emitted under a name, or skip numeric keys only when at least one named key exists.
🤖 Generated with Claude Code
- Dominant language
- Java
- Stars
- 13
- Forks
- 11
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 9
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from nf-core/nft-utils
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
nf-core/nft-utils#92 · 1 comment ·
Maintainers usually reply within 1 day
-
Bubble up some more errorsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
cleanup optionsOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
Maintainers usually reply within 1 day
All issues in nf-core/nft-utils
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
linagora/twake-calendar-side-service#1578 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
moneymanagerex/android-money-manager-ex#3122 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
tchiotludo/akhq#3438 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Paul-Austin-Oswego-CSC480-HCI521/gift-app#266 ·
Maintainers usually reply within 1 day