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

[Bug] The nexflow config field is not inherited correctly when changing Compute Environment #446

Open
mbosio85 opened this issue Aug 30, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@mbosio85
Copy link
Member

There is a mismatch between launches from the UI and the CLI when trying to launch a pipeline using a different compute environment than the one stored with the pipeline.

Minimal example

  • Create a CE "CE1" and set something in the nextflow config field (Staging option)
  • Create a second CE "CE2" and set a different text for the nextflow config field.
  • Create a pipeline and associate "CE1" to it.
    • Do not edit the nextflow config field so that it is inherited by the CE.
  • In the UI, launch the pipeline selecting "CE2" as Compute Environment
  • From the CLI do the same tw launch -c CE2 <pipeline>
  • Check the two runs
    • The run launched from the UI will have the nextflow config field correctly populated with the value from "CE2"
    • The run launched via the CLI will have the nextflow config field correctly populated with the value from "CE1"

Expected behavior

  • The run launched via the CLI will have the nextflow config field correctly populated with the value from "CE12
@mbosio85 mbosio85 added the bug Something isn't working label Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant