check out extensions for input files
Open
Nobody has claimed this yet.
bug
- Dominant language
- Nextflow
- Stars
- 202
- Forks
- 93
- Avg merge
- 1d 18m
- Merged PRs (30d)
- 15
Description
Description of the bug
with -r 1.11.0
No extension fails as expected
ERROR ~ ERROR: Validation of pipeline parameters failed!
-- Check '.nextflow.log' file for details
The following invalid input values have been detected:
* --input: string [id] does not match pattern ^\S+\.(csv|tsv|txt)$ (id)
but txt fails as well:
ERROR ~ Could not derive file type from /home/max/workspace/tests/id.txt. Please specify the file extension (CSV, TSV, YML and YAML are supported).
Command used and terminal output
No response
Relevant files
No response
System information
No response
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 reported behavior with -r 1.11.0 and an input ending in .txt, then inspect .nextflow.log alongside the two validation errors. Done means .txt input files are handled consistently with the supported CSV, TSV, YML and YAML extensions.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100