Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can SRA responses be trapped and reported in a user-friendly manner? #108

Open
telatin opened this issue Jul 14, 2022 · 1 comment
Open
Labels
enhancement Improvement for existing functionality

Comments

@telatin
Copy link

telatin commented Jul 14, 2022

Description of feature

Running:

nextflow run nf-core/fetchngs -r 1.7 --input list.txt --outdir sra -profile docker

Pipeline fails at NFCORE_FETCHNGS:SRA:SRA_IDS_TO_RUNINFO:

  [ERROR] The server couldn't fulfill the request.
  [ERROR] Status: 429 Too Many Requests

as the error is buried in the failed task report, it can be a bit intimidating so I was wondering if this kind of problems can be trapped and reported from the workflow itself (e.g. messages from the pipeline like parameter validation)

  • nextflow 21.10.6 build 5660
  • Cloud VM (OpenStack)
  • Executor: local
  • OS: "Ubuntu 20.04.3 LTS"
  • Container: Docker
  • fetchngs 1.7
@telatin telatin added the enhancement Improvement for existing functionality label Jul 14, 2022
@Midnighter
Copy link
Contributor

Looking for errors in the failed task logs is unfortunately quite normal when working with nextflow. I don't think we can/will do something about that. However, I would agree that the error message of the task itself is not very informative and can be improved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement for existing functionality
Projects
None yet
Development

No branches or pull requests

2 participants