Skip to content

Try-catch-finally not supported? #100

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

Open
jpfeuffer opened this issue Mar 14, 2025 · 2 comments
Open

Try-catch-finally not supported? #100

jpfeuffer opened this issue Mar 14, 2025 · 2 comments

Comments

@jpfeuffer
Copy link

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

Image

Unexpected input: 'finally'

@bentsherman
Copy link
Member

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

@bentsherman bentsherman transferred this issue from nextflow-io/vscode-language-nextflow Mar 14, 2025
@jpfeuffer
Copy link
Author

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.

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

No branches or pull requests

2 participants