We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
(Not sure if this should be a feature-issue or bug-issue, anyways here goes...)
Version 3.0.2 of Sarek contains a bunch of exit-statement. Here is an example:
exit
sarek/workflows/sarek.nf
Line 74 in bcd7bf9
I recently learned from Marcel Ribeiro-Dantas (@mribeirodantas) that those exit-statements should probably be replaced by exceptions like, say,
throw new Exception("Bad stuff happend")
since "if Nextflow is running in a subprocess of something else, it [an exit-statement] kills the entire thing".
What do you say we replace the exit-statements with exceptions?
The text was updated successfully, but these errors were encountered:
cf nf-core/rnaseq#978
Sorry, something went wrong.
FriederikeHanssen
Successfully merging a pull request may close this issue.
Description of feature
(Not sure if this should be a feature-issue or bug-issue, anyways here goes...)
Version 3.0.2 of Sarek contains a bunch of
exit
-statement. Here is an example:sarek/workflows/sarek.nf
Line 74 in bcd7bf9
I recently learned from Marcel Ribeiro-Dantas (@mribeirodantas) that those
exit
-statements should probably be replaced by exceptions like, say,throw new Exception("Bad stuff happend")
since "if Nextflow is running in a subprocess of something else, it [an exit-statement] kills the entire thing".
What do you say we replace the
exit
-statements with exceptions?The text was updated successfully, but these errors were encountered: