-
The API allows updating workflow contents - but not the workflow properties themselves - `name` and `stored_workflow_menu_entries` are obvious things to potential add to the `PUT` route for workflows.…
-
Ideally be inspired by OBF CoC.
-
Not sure how used this feature is, so perhaps this is niche, but I'm currently launching workflows with multiple datasets selected under an input in order to create multiple workflow invocations at on…
-
Spin out from discussion on #455 where is is good practice to defensively quote path and filenames in the `` template (etc?) when wrapping tools. This intended to cope with the corner case where Galax…
-
Add a tool syntax to document optional runtime variables a tool may consume - from standard variables such as ``GALAXY_SLOTS`` to tool specific such as ``TRINITY_MAX_MEMORY``.
After that is added -…
-
Shouldn't it be possible to uninstall a tool?
-
The reference genome is not displayed in the workflow editor. So I guess this needs to be a special cased in the editor. This is what we get after running the workflow. Rereunning the crashed tool wor…
-
I've seen this error reported every so often on the mailing list, but couldn't find an issue on it:
> An error occurred setting the metadata for this dataset
> Set it manually or retry auto-detect…
-
I consider tools that live in the `tools/` directory and do not rely on Galaxy internals (like collection tools) as builtin.
There are various (IMHO serious) problems with builtin tools:
1. they…
-
As a follow-up to #5516, it would probably be good to implement a checksum of the dataset, calculated on the client, sent to the server together with the dataset and verified when the chunked upload h…