-
Notifications
You must be signed in to change notification settings - Fork 441
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
Possible problem with data_manager_dada2 #2783
Comments
I found some time to look into this a bit (running Galaxy version 19.09) and I've found the cause, although I've not yet figured out the proper fix. It seems that the code here https://github.com/galaxyproject/galaxy/blob/dev/lib/galaxy/tools/data_manager/manager.py#L280 requires the
I believe there was some recent work on all data manager tools to properly handle multiple entries for the same data manager, but I didn't follow it closely enough to know the proper fix for this. So I'm hoping someone that was involved in that work can jump in here. The following hack does properly install the reference for use in Galaxy:
Hopefully this is just a trivial change to the data_manager_dada2 config file or something. :) |
Yeah, that looks broken, I'll have a look at that. It was introduced with galaxyproject/galaxy#8250 |
Ah, thanks very much @mvdbeek ;) |
galaxyproject#8250 introduced the add and remove keys for removing items from a data table. If there is a single data table definition incoming (meaning a dictionary) that does not specify the `add` key the new code would just ignore that entry and not move it. Fixes galaxyproject/tools-iuc#2783?
Thanks for the fix @mvdbeek ;) |
I installed the data2_data_manager locally and tried installing a reference dataset and it looks like the tool is not functioning correctly.
Here is the command line:
Here is the output.
But from what I've seen, nothing is moved into the Galaxy ~/tool-data directory.
This seems to have occurred on Galaxy test as well per galaxyproject/usegalaxy-playbook#273
The text was updated successfully, but these errors were encountered: