-
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
Workflows: tool version is replaced (randomly?) by older version #17273
Comments
Unclear how that is a bug ? If you don't have the tool installed what else are we supposed to do ? |
Both versions are installed. But might be related to #17272 (comment) On my instance I do not do a restart Galaxy after a tool installation. Maybe some "components" (handlers?) still have an old tool set. Will try a restart. |
I also see that from time to time when new tools get installed and web handlers have not been restarted. |
Windows style: Restart "solved" it. Question is, if this is expected. |
If everything is set up correctly and your processes are listening to the internal task queue, no. I've yet to see a reproduction. Whatever the problem, it's not related to workflows. |
and you can check that the task queue listening works with e.g. |
Describe the bug
In a workflow (galaxyproject/iwc#321) on my instance the tool version of the map_value tool is sometimes reduced to 0.1.1 (instead of 0.2.0 as defined in the workflow).
This happened a few times when opening the editor (but not always).
And also when I executed
planemo workflow_test_init --from_invocation 475029a28781f288 --galaxy_url https://galaxy.intranet.ufz.de --galaxy_user_key XXX
which showed me
bioblend WARNING: GET: error 500: b'{"err_msg": "Uncaught exception in exposed API method:", "err_code": 0}', 9 attempts left
. In the server logs was:Galaxy Version and/or server at which you observed the bug
Galaxy Version: 23.1
Commit: 0e3a0ca
The text was updated successfully, but these errors were encountered: