Tunc Kayikcioglu: I think that is basically the way to go.
Problem is that you can (probably) not simply add a new column to an existing data table because either admins would need to update old entries (adding some mock value to the new column) or Galaxy would need a way to return a default value if a column is accessed that does not exist in the requested row (I'm not sure if this actually works .. but I doubt it).
So, you can't propagate to old versions.
What we did before is to create a new datatable that contains the new version column.
with "old tool" you mean the data manager?
If we deprecate it, then nobody can add new entries to the select ..
--mpa3
parameter does not make much sense .. or?
Just checked. The --mpa3
flag allows you to use old databases (I had a user error report who wanted to use metaphlan4 with an old database .. and new databases can't be downloaded at the moment since the new data manager has not been deployed to the toolshed).
So my suggestion would be to ask upstream if they plan to make the old databases available. Then we would need to create a new data table supporting the version .. and trigger --mpa3
if a v3 database is selected.
Alternatively, we could decide to not support --mpa3
and only use the v4 DB (which still would require the new data table .. be safe for the future).
If you like we can continue elsewhere .. e.g. in an issue/PR .. if you like. Just ping me.
main
? I think that's what causing the planemo autoupdate GitHub workflows to fail for tools-iuc
No idea Cristóbal Gallardo why the collection is not shown. Just checked on my 22.01 and 22.05 instances with a collection containing a fasta and a txt .. without any problems.
Can you try with such a toy example?
Or download the collection and reupload (maybe also to another galaxy) ..
Hi all, I found a problem when trying to extract elements from a collection consisted in heterogeneous datatypes; ...
Expression Tools
or Workflow Tools
category on the tool shed ?
pick_value
expression tool to the IUC, and I really can't think of a matching category (plus some of the other existing expression tools are rather odd fits in the text manipulation category)
The image itself is embedded with
.. image:: $PATH_TO_IMAGES/flank-glyph.png
.. class:: warningmark
and the images are in static/images
The following image definitions are all supported. The former $PATH_TO_IMAGES is no longer
required, and is now ignored.
.. image:: https://raw.github.com/galaxy/some_image.png
.. image:: $PATH_TO_IMAGES/some_image.png
.. image:: /static/images/some_image.gif
.. image:: some_image.jpg
.. image:: /deep/some_image.png
This is super interesting and should be somewhere in tools-iuc.
Huh:
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
https://github.com/galaxyproject/tools-iuc/actions/runs/4008074858
tools/bakta/bakta.xml
uses it as grep amrfinderplus_database tools -r --include "*xml"
revealed