Cheaha strict syntax conversion #1047
Conversation
|
I think it's the plugin that's wrong here, And you don't need/shouldn't do You can go ahead and try this on your cluster. |
|
This will also still fail because the parameter is function closure now, you can directly move the closure to the input of |
|
But that closure is called with the expected parameters, so I'm not sure why it should fail? I agree there's no point in having it in params though (and having it there likely gives warnings about it that should be dealt with by telling nf-schema to ignore it). |
|
Hey all - excellent, I will make these changes and test it in our cluster and update this PR asap. Especial thanks for the clarification that I can safely ignore the Nexflow plug-in message (and before submitting this PR I did actually try to just directly provide the closure but the plug-in message was still there which generated confusion). Either thanks! Will update here soon. |
|
@nvnieuwk : changes are made and tested with Edit: some automated checks failing below but on other profiles - let me know if there is anything on this end to be addressed. |
|
@lianov can you try merging |
|
@jfy133 : done - looks like some tests are still failing but the cheaha one went through (merging is still blocked though). |
Yeah, this will take time - but at least we confirm Cheaha passes, so we can force merge for you! |
name:
cheahaprofilePlease follow these steps before submitting your PR:
[WIP]in its titlemasterbranchIssue #1020
@nvnieuwk : here is the requested PR. As a recap, currently the Nextflow VS Code plugin complains about line 66 with the message
Config option 'process.queue' with type String cannot be assigned to value with type ClosurePlease also note that I have not enabled
.call()(yet) line 54 as I was attempting a fix for the warning above. Thanks!As a note, if we can solve this here, I will still need to test the profile in our cluster before moving forward with the merge.