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

There is no limit for file sizes or execution times #7

Open
efcaguab opened this issue May 28, 2021 · 0 comments
Open

There is no limit for file sizes or execution times #7

efcaguab opened this issue May 28, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@efcaguab
Copy link
Contributor

A particularly large Fastq file could create problems to the server and make us incur in unanticipated costs. There should be a mechanism (ideally both on the client and the server) preventing the processing of extremely large files.

Similarly, an unanticipated error might cause the API to extend the computation time which, again, might incur in unanticipated costs. There should be a mechanism to kill the API if a threshold is exceeded.

@efcaguab efcaguab added the enhancement New feature or request label May 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant