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

Python Runners: Activation Option to disable the service from being executed #1805

Open
AntoninoMarioC opened this issue Nov 29, 2024 · 4 comments
Assignees
Labels
a:pipeline-services Feedback Feedback through frontend type:enhancement Feature requests (functionality and UI)

Comments

@AntoninoMarioC
Copy link
Member

Describe the user role
As a user I would like to enable/disable some python runner services in my pipelines, e.g. because I have already the data that the service produces. It would be great if this enabling/disabling parameter could be set on the service settings already, or provided as an integer or in the input files.

Describe the goal

Describe the benefit

Additional context

@AntoninoMarioC AntoninoMarioC added Feedback Feedback through frontend type:enhancement Feature requests (functionality and UI) labels Nov 29, 2024
@AntoninoMarioC
Copy link
Member Author

In addition to this case, I would consider options to enable/disable changes of service's input and output files. For example, I would like to disable a service from a pipeline, but keep the service being connected to another service providing its unmodified output files.

@JavierGOrdonnez
Copy link
Contributor

I believe that if you click "Run", only the non-up-to-date runners (e.g. those for which the input has changed) will be run

@odeimaiz
Copy link
Member

odeimaiz commented Dec 5, 2024

Also if you want to Run a subset of nodes, you can multi select them and "Run Selection"

Run Selection:
RunSelection

Run (those non-up-to-date will run):
RunNonUpToDate

@AntoninoMarioC
Copy link
Member Author

Thanks @odeimaiz and @JavierGOrdonnez, this partially solves the problem but it is not robust to errors. The user may select wrongly or push the button wrongly to run all the services, and it may loose a lot of computational time. There may be the need to lock and enable services so that the risk is removed. As well, options to hide services would be good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:pipeline-services Feedback Feedback through frontend type:enhancement Feature requests (functionality and UI)
Projects
None yet
Development

No branches or pull requests

6 participants