Skip to content

Conversation

@cgoina
Copy link
Contributor

@cgoina cgoina commented Nov 12, 2025

@krokicki @neomorphic @allison-truhlar
This is related to https://app.clickup.com/t/86ad02fne story for starting the discussion about task plugins.

So far there is a mechanism to register these plugins with the python setuptools entry points and there's a generic task that could potentially run any nextflow workflow.

The parameters returned are based on the metadata from argparse parameters and since it is not tied to a specific pipeline it does not know how to get the parameters that could be defined in the pipeline's nextflow_schema.

The exposed endpoints are also very limited and there's no UI - just very few apis related to getting available tasks, the parameters and starting a new tasks.
The corresponding model is defined but nothing is persisted in the db yet. Getting the task status will also depend on that.

migrate = "alembic upgrade head"
migrate-create = "alembic revision --autogenerate"
migrate = { cmd = "alembic upgrade head", cwd = "fileglancer" }
migrate-create = { cmd = "alembic revision --autogenerate", cwd = "fileglancer" }
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes are actually needed for these tasks to work. I also updated development docs with a section for database changes.

ignore = ["W002"]

[tool.pixi.project]
[tool.pixi.workspace]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think @neomorphic was already asking to make this change

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

Successfully merging this pull request may close these issues.

2 participants