-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Activating the "modules" dependency resolver prevent a Galaxy instance to start properly #4452
Comments
Introduced in #3444 . Probably the easiest solution is to add an empty |
…ency resolvers. None of this broke the functionality but it made it harder to get going with and obsecured errors. Fixes galaxyproject#4452 I think - thanks @arbernard.
@mvdbeek I just noticed you self-assigned this issue - I didn't notice that before I started hacking on it - sorry. I'm missing a lot of details today. |
I didn't do anything yet, no worries. |
On branch release_18.05 : the issue is still here. |
Should be fixed by #7398, many thanks to @FredericBGA |
If you try to uncomment the "modules" dependency resolver in the dependency_resolvers_conf.xml file and try to start the Galaxy instance then it will fail with the following errors:
The message in the log file is a bit more explicit:
There is indeed no such file in the config folder of recent Galaxy version.
I didn't found any documentation about this file yet.
The text was updated successfully, but these errors were encountered: