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
Galaxy should refuse to load tool if tool is too new (tool profiles) #2086
Comments
Galaxy should show warnings? (this is during tool installation right?) |
Yes, that's the correct phrasing. (Sorry, I woke up 5 minutes after the conference call started this morning) |
@erasche sorry we woke you up and thanks for joining! 👏 |
From #4361: This came up during the GCC (and the last GCC as well, I think ...). We can probably not rely on this retroactively, but we should have a mechanism in place so that in the future we can change certain defaults. So what I would propose is that galaxy refuses to load a tool with a profile version higher than the running galaxy version, and that the toolshed installation process will inspect a repository for the minimum required galaxy version. |
We look at a tools profile attribute, and if it is too new we will not load the tool. This is a first step towards galaxyproject#2086
We look at a tools profile attribute, and if it is too new we will not load the tool. This is a first step towards galaxyproject#2086
Wonderful - thanks for the additional @mvdbeek - this is great! |
The text was updated successfully, but these errors were encountered: