You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is a bug or really not supported by nextflow but I get errors from the checker when using try-catch-finally. In my case in the workflow.onComplete block
Unexpected input: 'finally'
The text was updated successfully, but these errors were encountered:
I didn't include finally in the strict syntax because I wasn't sure if it would be needed. I'm open to supporting it, it's not a big deal, but I wonder if there is a way to do what you want without a finally clause. I don't think the disconnect() is strictly needed here
Hmm yeah I can't judge. I agree that it might not be absolutely necessary here, although nice-to-have.
I guess if it does not interfere with anything that could break a flow it would not hurt supporting it.
This was my first need for a finally.
Hi!
Not sure if this is a bug or really not supported by nextflow but I get errors from the checker when using try-catch-finally. In my case in the workflow.onComplete block
Unexpected input: 'finally'
The text was updated successfully, but these errors were encountered: