You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In release_24.2 if I set enable_tool_tags to True in galaxy.yml and then add a tags attribute to a tool_conf file entry I get the following stack trace and the tool does not load.
In addition, the tool_tag_association table has 0 rows because the enable_tool_tags config value is false.
The only trace I could find about this feature is an ancient commit from 2011 03908bc and the commit message implies it may have never been fully implemented? Or maybe it broke long ago...
What should we do here?
Add a relationship to the Tag model that will probably fix the issue, but at the same time also bring an undead feature back to life... 🧟
Deprecate or completely remove the use of tags for tools. Dropping this table, models, logic, etc. since it seems tool labels might cover the general use case without all the other complexity.
I would do this. I don't think this pressing but we should at some point delete the cruft left over from 03908bc and write a database migration to drop the table.
In release_24.2 if I set enable_tool_tags to True in galaxy.yml and then add a tags attribute to a tool_conf file entry I get the following stack trace and the tool does not load.
Also tagged_tools isn't really found elsewhere in the code as far as I can tell:
Maybe it used to be a dynamic property setup in the model layer? Found while trying to test https://github.com/galaxyproject/galaxy/pull/19076/files but that PR clearly did not cause this issue.
The text was updated successfully, but these errors were encountered: